CNV-37629: Keep name when configuring existing SSH key in same namespace #1751
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.
📝 Description
When configuring an existing SSH secret for the namespace in which that secret resides in the "Manage SSH keys" section the UI displays the secret name with a randomly generated suffix. In actuality, that secret wasn't created and doesn't exist. This can be demonstrated by navigating away from that screen and returning to it. Upon doing so "Not configured" will be displayed for that namespace instead of the generated secret name.
This PR makes it so that the existing secret is used instead of generating a new name.
Jira: https://issues.redhat.com/browse/CNV-37629