-
Notifications
You must be signed in to change notification settings - Fork 56
Open
Description
In our setup we'd like to be able to declaratively deploy an internal and external Group and have the external Group as member of the internal one.
Currently it seems that one has to specify the member groups in group.redhatcop.redhat.io.spec.memberGroupIDs with an ID. But this ID is obviously only available after the referenced object is created.
So currently the Workflow to create these objects looks like this
- Deploy Manifest for external Group
- Use Vault-UI or CLI to read out the ID of this group
- Deploy Manifest for internal Group referencing the ID from step 2
This introduces a manual step in an otherwise declarative approach which does not spark joy ;)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels