-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update oblt-cli/version updatecli policy #85
Update oblt-cli/version updatecli policy #85
Conversation
update-compose.yaml
Outdated
@@ -2,7 +2,7 @@ | |||
# https://www.updatecli.io/docs/core/compose/ | |||
policies: | |||
- name: Handle default oblt-cli version | |||
policy: ghcr.io/elastic/oblt-updatecli-policies/oblt-cli/version:0.0.2@sha256:dd79537aa64a28c57da351182a70a2a798e9b6c5eb55c243fdbd4f5bffe5133d | |||
policy: ghcr.io/elastic/oblt-updatecli-policies/oblt-cli/version:0.0.3@sha256:8b996fc5e4351610117ad87e0cc74f562c8228c967a5dde0ed2f9c28f1935c3c |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you wanna try the auto-update you recently added here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about the same.. but then I thought, I need to update the config anyway.. but still.. let me try.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Failed, unfortunately. https://github.com/elastic/oblt-actions/actions/runs/9859667131
At least, I can try to fix it in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
were you able to make the autodiscovery update work in another repo?
I'm wondering if it's failing because it cannot read the oblt-cli/version policy package
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It worked in elastic/apm-agent-go#1634 when running https://github.com/elastic/apm-agent-go/actions/runs/9809715657 as part of elastic/apm-agent-go#1633, for such I created a feature branch in the upstream
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know what's the error about:
⚠ While nothing change in the current pipeline run, according to the git history, some commits must be pushed
ERROR: non-fast-forward update
ERROR: push error: unpack error: index-pack failed
There is a missing piece of configuration:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think you can remove the bump and keep the rest of the files so we can test the updatecli itself by running the main branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.