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

failed when promote snap using option: --yes #4312

Closed
boukendesho opened this issue Aug 10, 2023 · 6 comments
Closed

failed when promote snap using option: --yes #4312

boukendesho opened this issue Aug 10, 2023 · 6 comments
Labels
Bug Actual bad behavior that don't fall into maintenance or documentation

Comments

@boukendesho
Copy link

Bug Description

I want to promote a snap without confirmation, so i use --yes option

To Reproduce

snapcraft promote SNAP_NAME --from-channel latest/edge --to-channel latest/candidate --yes

then i got

Error: 'latest/edge' is not a valid set value for --from-channel when using --yes.

Environment

Ubuntu 23.04
snapcraft 7.5.2

snapcraft.yaml

no

Relevant log output

no log

Additional context

No response

@boukendesho boukendesho added the Bug Actual bad behavior that don't fall into maintenance or documentation label Aug 10, 2023
@boukendesho
Copy link
Author

snapcraft promote SNAP_NAME --from-channel edge --to-channel candidate --yes

drop the 'latest/' track name also got same error

@sergiusens
Copy link
Collaborator

Thanks for the report. Is the error confusing? what we are essentially saying is that you shouldn't be auto promoting from edge as it is a moving target

@boukendesho
Copy link
Author

@sergiusens Yeah a bit confusing to me, so this is a normal behavior by design? I want to automatically promote through cron tasks. Is there any way to do this currently?

@sergiusens
Copy link
Collaborator

Not currently, but we can consider adding a flag like --enable-dangerous-promotion. Since edge is a moving target, there is no set that can be created from edge in a reliable way. We could also consider creating sets with version and/or build ids (launchpad and our action-build add these)

@boukendesho
Copy link
Author

@sergiusens ok, thx

@krille-chan
Copy link

krille-chan commented Sep 18, 2023

This got closed, does it mean that --enable-dangerous-promotion is now implemented?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Actual bad behavior that don't fall into maintenance or documentation
Projects
None yet
Development

No branches or pull requests

3 participants