Skip to content
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

ci: add logql-analyzer CI #14495

Merged
merged 7 commits into from
Oct 16, 2024
Merged

ci: add logql-analyzer CI #14495

merged 7 commits into from
Oct 16, 2024

Conversation

trevorwhitney
Copy link
Collaborator

What this PR does / why we need it:

Adds logql-analyzer CI that got removed with the drone removal.

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

@trevorwhitney trevorwhitney requested a review from a team as a code owner October 15, 2024 20:44
Copy link
Contributor

@vlad-diachenko vlad-diachenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that we need to address the comments before the merge.

Comment on lines 66 to 69
echo $PLUGIN_CONFIG_TEMPLATE > updater-config.yaml
# replace placeholders with RELEASE_NAME and RELEASE TAG
sed -i "s/\\"{{release}}\\"/\\"$RELEASE_NAME\\"/g" %s % configFileName
sed -i "s/{{version}}/$RELEASE_TAG/g" %s % configFileName
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we do not need this line because the config is created on the next step

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, it's a JSONNET ;)

"update_jsonnet_attribute_configs": [
{
"file_path": "ksonnet/environments/logql-analyzer/supported-versions.libsonnet",
"jsonnet_key": "${RELEASE_NAME}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are ENV variables shared between the steps?
I see that Run shell command step exports it but I am not sure if they are available on this step

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, good call, they either need to be echoed into $GITHUB_ENV or set using the ::set-output syntax, which I opted for

@trevorwhitney trevorwhitney merged commit 08f6d29 into main Oct 16, 2024
60 checks passed
@trevorwhitney trevorwhitney deleted the logql-analyzer-ci branch October 16, 2024 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants