fix: adds service account to keystone argo event source #542
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed my test tenants aren't getting deleted in nautobot when I delete them in keystone. Upon investigating, I found the argo event is failing with an error regarding the service account:
I believe the default user is old.. it's mentioned in https://github.com/rackerlabs/understack/blob/main/components/argo-events/default-role.yaml but this file seems unused. The other workflows are using a
workflowuser, so I set this keystone workflow to the same, and the argo events are successfully completing now, and the projects are getting deleted in nautobot as expected.