New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: twingateresourceaccess - allow specifying principal by name #62
feat: twingateresourceaccess - allow specifying principal by name #62
Conversation
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
This pull request is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
…-specifying-principal-by-name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix & merge!
deploy/twingate-operator/crds/twingate.com.twingateresourceaccesses.yaml
Outdated
Show resolved
Hide resolved
deploy/twingate-operator/crds/twingate.com.twingateresourceaccesses.yaml
Show resolved
Hide resolved
"fieldsV1": { | ||
"f:spec": { | ||
".": {}, | ||
"f:principalId": {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be principalExternalRef
? Or this metadata
key is not used in the test? If so, maybe it's simpler to not include it 🤔
…-specifying-principal-by-name
…-specifying-principal-by-name
…-specifying-principal-by-name
Pull Request Test Coverage Report for Build 8431132151Details
💛 - Coveralls |
…-specifying-principal-by-name
Related Tickets & Documents
Resolves #32
Changes
Adds support for
principalExternalRef
in theTwingateResourceAccess
CRD.