Use repo var for JIRA_HOST #14270
Merged
Use repo var for JIRA_HOST #14270
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
momentmaker
approved these changes
Aug 29, 2024
|
erikburt
approved these changes
Aug 29, 2024
erikburt
deleted the
RE-2932-replace-jira-host-secret-with-a-repository-variable-instead
branch
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.
We can’t have
JIRA_HOSTbe a secret, since thesolidity-foundry-artifacts.ymlfile posts a Jira URL that contains a link to all issues that are a part of the SBOM.It’s fine to make non-secret since the Jira host URL is exposed everywhere in the codebase, it’s not a secret value to begin with.