We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have a scenario where we have RBAC enabled with which docker trigger doesn't work.
For that we have enabled pipeline permissions in Spinnaker, as provided in the documentation.
https://spinnaker.io/docs/setup/other_config/security/authorization/pipeline-permissions/
But after enabling pipeline permissions the roles section form the dinghymodules in not getting reflected in the UI
"roles": [ "AD-groupo-object-ID" ]
manual addition of the AD group from the UI works where as from dinghy modules it doesn't
Could you please help on this
The text was updated successfully, but these errors were encountered:
Do you have an example of your stage/pipeline code? I am using the YAML format and it does seem to be working as expected for me
Sorry, something went wrong.
No branches or pull requests
We have a scenario where we have RBAC enabled with which docker trigger doesn't work.
For that we have enabled pipeline permissions in Spinnaker, as provided in the documentation.
https://spinnaker.io/docs/setup/other_config/security/authorization/pipeline-permissions/
But after enabling pipeline permissions the roles section form the dinghymodules in not getting reflected in the UI
"roles": [
"AD-groupo-object-ID"
]
manual addition of the AD group from the UI works where as from dinghy modules it doesn't
Could you please help on this
The text was updated successfully, but these errors were encountered: