Assume yes when using microdnf
#10157
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jakub Scholz <[email protected]>
|
/azp run acceptance |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ppatierno
approved these changes
May 25, 2024
see-quick
approved these changes
May 25, 2024
im-konge
approved these changes
May 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
It looks like for some reason, some of the
microdnfcommands in our Dockerfiles now require confirmation. There does not seem to be any change locally, so likely something changed either in Azure or in howmicrodnfdetects interactive / non-interactive terminals. This PR adds the confirmations to avoid the CI pipelines being stuck.