fix conda and podman profile strictness #972
Merged
Conversation
This file contains hidden or 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
jfy133
approved these changes
Mar 26, 2021
Member
|
Oops, nice catch @phue ! Feel free to merge! |
Member
|
Ah missing CHANGELOG but otherwise GTG |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In #866, we increased the strictness for container profiles by explicitly disabling other container engines if a profile is selected.
Right now nothing is broken per se, but for the
condaandpodmanprofiles, we currently do not disablecharliecloudproperly. This fixes it.PR checklist
CHANGELOG.mdis updateddocsis updated