Proposal: add CRDs for managing users, roles, repositories, assignments, etc.

[AndersBennedsgaard]

Is your feature request related to a problem? Please describe.

We have set up Pulp as a Python repository on a multi-tenant environment. That requires setting up users, roles, repositories, remotes, etc. using the pulp CLI, instead of using our Infrastructure-as-Code (GitOps, rather), which makes it hard to manage across multiple environments.

Describe the solution you'd like

I would like a way to set up all of these different resources, using the operator.
That means either creating a bunch of very small CRDs that is basically a wrapper for pulp <resource> create ..., or a single CRD which defines a complex relationship between all of the resources.
I would guess the code would be simpler with "micro-CRDs", but that might create some duplication of code 🤔

Describe alternatives you've considered

Create a script which runs as a Job on my clusters. This will be a manual process, and will most likely break at some random point in the future

[mikedep333]

Hi @AndersBennedsgaard ,

This is a duplicate of #1263 . However, you have additional details that are valuable to the design, so I will make note of that in #1263.