Closed giacoliva closed 10 months ago
Hi @giacoliva. Thanks for your PR.
I am @kingmakerbot. You can interact with me issuing a slash command in the first line of a comment. Currently, I understand the following commands:
/rebase
: Rebase this PR onto the master branch/merge
: Merge this PR into the master branch/hold
: Adds hold label to prevent merging with /merge/unhold
: Removes the hold label to allow merging with /merge/deploy-staging
: Deploy a staging environment to test this PR (the build-all
flag enables user environments building)/undeploy-staging
: Manually undeploy the staging environmentMake sure this PR appears in the CrownLabs changelog, adding one of the following labels:
kind/breaking
: :boom: Breaking Changekind/feature
: :rocket: New Featurekind/bug
: :bug: Bug Fixkind/cleanup
: :broom: Code Refactoringkind/docs
: :memo: Documentation/deploy-staging
/deploy-staging
/merge
/merge
Your staging environment has been correctly teared-down!
Description
Workspaces can now set AutoEnroll features with two flags in the Spec (no auto enroll / enroll request and manager's approval / completely self enroll) Tenants can now autoenroll in Workspaces enabled (with
user
orcandidate
role depending on settings)Tenants are able to edit themselves in order to add or remove Workspaces with
autoEnroll
enabledHow Has This Been Tested?
Environment: KinD with CRDs installed, Tenant Operator and Webhooks running. Keycloak not configured.
kubectl
api - Tenant edit as root userkubectl
api - Tenant edit as tenant user role (kubectl --as <tenantname>
)kubectl
api - Workspace edit as root usergraphql
- Tenant & Workspace edit as default user