Replace old cloud app credentials in the vault #1180
Closed
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
with the one for the new cloud created using the service account
|
Will this break a few Jenkins apps? |
|
Nope, I have added dedicated Jenkins credentials and reconfigured only one project to use the new one. The rest will follow a bit later. This change will only affect the |
|
I have also updated the creds stored in |
|
Closing this PR and will reopen a new one due to the conflict in the vault file which cannot be resolved. |
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 created "general-purpose" app credentials in our new cloud, which we can use for cron jobs, telegraf, and others. This PR replaces the old cloud app credentials in the vault with the ones for the new cloud created using the service account, thus removing the credentials associated with any of the admin user accounts.