feat(workflow): add random hash generation for console password in test-legacy-upgrade #513
Conversation
This file contains hidden or 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
…st-legacy-upgrade - Added a step to generate a random hash for the console password using /dev/urandom. - Updated the params.json creation to use the generated hash instead of a fixed secret. - Ensured the hash is printed for debugging purposes.
- Fixed the syntax for generating a random hash for the console password using /dev/urandom. - Ensured proper escaping of special characters in the tr command.
- Removed the push event trigger to streamline the workflow execution. - The workflow will now only trigger on pull requests affecting .github/workflows/**/*
ragingra
approved these changes
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Provide a detailed description of all the changes present in this pull request.
Checklist
Changes include test coverage?
Have you updated the documentation?