Add parameter to allow configured secrets #8
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
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.
Hello :)
This PR adds a new parameter
allowed_patternsthat can be configured with a JSON file. This can be used to avoid failed runs when we want to have a secret (like test keys) in the repository.I tested it with your own repository, using this pattern file:
{ "some key": "1:283108921048:web:d2bd16290170357a9391da", "other key": "1:283108921048:web:d2bd16290170357a9391ad" }Regarding the refactor of
entrypoint.sh, I started fixing a few shellcheck warnings and got to a point where I couldn't fix it while keeping the old style. So I rewrote it 😓