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

Confirm all flag (for automation) #275

Open
Daverkex opened this issue Feb 20, 2019 · 5 comments
Open

Confirm all flag (for automation) #275

Daverkex opened this issue Feb 20, 2019 · 5 comments

Comments

@Daverkex
Copy link

Like apt-get install X -y this tool need a flag for automatic updates like Ansible o similar software.

I try to update Raspberry firmware and my Ansible play fail because rpi-update promp for a major update in the kernel.

@popcornmix
Copy link
Collaborator

Try setting SKIP_WARNING=1 in environment if you don't won't want to be prompted by warnings.
But be aware the warnings are there for a reason.

@Daverkex
Copy link
Author

Daverkex commented Feb 28, 2019

Thanks @popcornmix
SKIP_WARNGING=1 working for me.
Maybe is a good idea add this flag in the README?

I know that skip the warnings in general is a bad idea but this automation is part of a boostrap, clean installation and up to date. I need update if the warning is a new kernel. Any idea for only allow this condition with the rpi-update (out of arkane magic with the managament tool)? I think that skip all warnings can be a problem.

@lurch
Copy link
Contributor

lurch commented Jun 8, 2019

@Daverkex It's not clear what you mean by "I need update if the warning is a new kernel ... I think that skip all warnings can be a problem." ?

@Daverkex
Copy link
Author

Sorry for my late answer.
Skip all warning with only a flag ca be a problem. In my case I only need skip if the warning is a new kernel. The automation need fail if other unspected warnings happens.
For this reason I think that a good idea is add a special flag to skip the warning if is a new kenel and other for skip all.

@lurch
Copy link
Contributor

lurch commented Dec 16, 2019

Ahhh. I don't think that the warning-mechanism has a "reason for the warning" flag that you seem to be looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants