CRAYSAT-1913: Remove the ability to read VCS password from a file #276
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
annapoorna-s-alt
force-pushed
the
CRAYSAT-1913-remove-vcs
branch
from
3360988
to
7c9300f
Compare
haasken-hpe
approved these changes
Oct 18, 2024
| ## [3.32.7] - 2024-10-15 | ||
|
|
||
| ### Fixed | ||
| - Remove the ability to read VCS password from a file which is no longer necessary. |
There was a problem hiding this comment.
Might clarify that this applies to sat bootprep. Does it apply anywhere else?
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.
Summary and Scope
Remove the ability to read VCS password from a file which is no longer necessary.
Issues and Related PRs
Resolves CRAYSAT-1913.
Testing
List the environments in which these changes were tested.
Tested on:
<development system>Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist