phase2: update default sdk pattern to a more relaxed pattern #28
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
|
@Ansuel - there's a slight type in the commit subject. |
Update default sdk pattern to a more relaxed pattern to make it future proof if in the future the compression extension will change again. Needed currently with the migration from .xz to .zst. Signed-off-by: Christian Marangi <[email protected]>
Ansuel
changed the title
aparcar
approved these changes
Apr 12, 2024
|
I've it already prepared in Ansible, just not deployed yet, will do today. |
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.
Update default sdk pattern to a more relaxed pattern to make it future proof if in the future the compression extension will change again.
Needed currently with the migration from .xz to .zst.
@ynezz @f00b4r0 Can you guys also update the config.ini to point to the new pattern (if that is defined in our config?)
Or eventually if it's not and we can't push a new release, can we add the entry since that is configurable?