Skip to content

chore(CI): Add image building for querytee in pr/release workflows; add multi-arch support for querytee #18703

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JordanRushing
Copy link
Contributor

What this PR does / why we need it:

With the addition of Goldfish mode for querytee (#17959) we now want to build and publish querytee images when:

  1. Changes to querytee are merged to main
  2. On a weekly cadence similar to other Loki components

Which issue(s) this PR fixes:

N/A

Special notes for your reviewer:

N/A

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

…dd multi-arch support for querytee

Signed-off-by: Jordan Rushing <[email protected]>

permissions:
contents: read
id-token: write

Check failure

Code scanning / zizmor

id-token: write is overly broad at the workflow level Error

id-token: write is overly broad at the workflow level
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant