API: Disallow duplicate ssh keys #959
Merged
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
|
I added a script to run after deployment to generate fingerprints for all existing ssh keys, but I'm stuck on how to make it work "properly" (like the other scripts in |
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.
Checklist
When the API has duplicate api keys in the system, it causes problems with some parts of lagoon. This adds a unique key constraint to the api db via ssh key fingerprints, and updates the api to save/get said fingerprints.
Changelog Entry
Bugfix - API no longer allows adding duplicate ssh keys (#577)
Closing issues
Closes #577