Update mimir-prometheus on branch pushes #11518
Draft
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This comment has been minimized.
This comment has been minimized.
dimitarvdimitrov
force-pushed
the
dimitar/build/actions/listen-for-mimir-prometheus-updates
branch
from
d3a57c5 to
6b4b612
Compare
dimitarvdimitrov
changed the base branch from
main
to
dimitar/build/add-workflow-to-update-mimir-prometheus
Comment on lines
30
to
41
| run: | | ||
| if [ "${{ github.event_name }}" = "repository_dispatch" ]; then | ||
| # For repository_dispatch, use the branch_name from client_payload for mimir_prometheus_branch. | ||
| # The main use case is for weekly branches, so we just use the same branch name here too. | ||
| MIMIR_PROMETHEUS_BRANCH="${{ github.event.client_payload.branch_name }}" | ||
| MIMIR_BRANCH=$MIMIR_PROMETHEUS_BRANCH | ||
| echo "Triggered by repository_dispatch" | ||
| echo "Using mimir-prometheus branch from payload: $MIMIR_PROMETHEUS_BRANCH" | ||
| else | ||
| # For workflow_dispatch, use the input values | ||
| MIMIR_BRANCH="${{ inputs.mimir_branch }}" | ||
| MIMIR_PROMETHEUS_BRANCH="${{ inputs.mimir_prometheus_branch }}" | ||
| echo "Triggered by workflow_dispatch" | ||
| echo "Using input values - mimir branch: $MIMIR_BRANCH, mimir-prometheus branch: $MIMIR_PROMETHEUS_BRANCH" | ||
| fi | ||
|
|
||
| echo "mimir_branch=$MIMIR_BRANCH" >> $GITHUB_OUTPUT | ||
| echo "mimir_prometheus_branch=$MIMIR_PROMETHEUS_BRANCH" >> $GITHUB_OUTPUT |
Check failure
Code scanning / zizmor
github.event.client_payload.branch_name may expand into attacker-controllable code
Comment on lines
30
to
41
| run: | | ||
| if [ "${{ github.event_name }}" = "repository_dispatch" ]; then | ||
| # For repository_dispatch, use the branch_name from client_payload for mimir_prometheus_branch. | ||
| # The main use case is for weekly branches, so we just use the same branch name here too. | ||
| MIMIR_PROMETHEUS_BRANCH="${{ github.event.client_payload.branch_name }}" | ||
| MIMIR_BRANCH=$MIMIR_PROMETHEUS_BRANCH | ||
| echo "Triggered by repository_dispatch" | ||
| echo "Using mimir-prometheus branch from payload: $MIMIR_PROMETHEUS_BRANCH" | ||
| else | ||
| # For workflow_dispatch, use the input values | ||
| MIMIR_BRANCH="${{ inputs.mimir_branch }}" | ||
| MIMIR_PROMETHEUS_BRANCH="${{ inputs.mimir_prometheus_branch }}" | ||
| echo "Triggered by workflow_dispatch" | ||
| echo "Using input values - mimir branch: $MIMIR_BRANCH, mimir-prometheus branch: $MIMIR_PROMETHEUS_BRANCH" | ||
| fi | ||
|
|
||
| echo "mimir_branch=$MIMIR_BRANCH" >> $GITHUB_OUTPUT | ||
| echo "mimir_prometheus_branch=$MIMIR_PROMETHEUS_BRANCH" >> $GITHUB_OUTPUT |
Check failure
Code scanning / zizmor
inputs.mimir_branch may expand into attacker-controllable code
Comment on lines
30
to
41
| run: | | ||
| if [ "${{ github.event_name }}" = "repository_dispatch" ]; then | ||
| # For repository_dispatch, use the branch_name from client_payload for mimir_prometheus_branch. | ||
| # The main use case is for weekly branches, so we just use the same branch name here too. | ||
| MIMIR_PROMETHEUS_BRANCH="${{ github.event.client_payload.branch_name }}" | ||
| MIMIR_BRANCH=$MIMIR_PROMETHEUS_BRANCH | ||
| echo "Triggered by repository_dispatch" | ||
| echo "Using mimir-prometheus branch from payload: $MIMIR_PROMETHEUS_BRANCH" | ||
| else | ||
| # For workflow_dispatch, use the input values | ||
| MIMIR_BRANCH="${{ inputs.mimir_branch }}" | ||
| MIMIR_PROMETHEUS_BRANCH="${{ inputs.mimir_prometheus_branch }}" | ||
| echo "Triggered by workflow_dispatch" | ||
| echo "Using input values - mimir branch: $MIMIR_BRANCH, mimir-prometheus branch: $MIMIR_PROMETHEUS_BRANCH" | ||
| fi | ||
|
|
||
| echo "mimir_branch=$MIMIR_BRANCH" >> $GITHUB_OUTPUT | ||
| echo "mimir_prometheus_branch=$MIMIR_PROMETHEUS_BRANCH" >> $GITHUB_OUTPUT |
Check failure
Code scanning / zizmor
inputs.mimir_prometheus_branch may expand into attacker-controllable code
This comment has been minimized.
This comment has been minimized.
dimitarvdimitrov
force-pushed
the
dimitar/build/actions/listen-for-mimir-prometheus-updates
branch
from
6b4b612 to
182e520
Compare
|
😢 zizmor failed with exit code 14. Expand for full output |
Base automatically changed from
dimitar/build/add-workflow-to-update-mimir-prometheus
to
main
May 23, 2025 18:49
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
dimitarvdimitrov
force-pushed
the
dimitar/build/actions/listen-for-mimir-prometheus-updates
branch
from
13f7290 to
4e78462
Compare
Signed-off-by: Dimitar Dimitrov <[email protected]>
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.
This pull request enhances the
update-vendored-mimir-prometheus.ymlworkflow by introducing support for triggering updates viarepository_dispatchevents triggered by grafana/mimir-prometheus#877