DO NOT MERGE - Package sync tool and updated syncing docs #274
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: Matt Wrock <[email protected]>
mwrock
force-pushed
the
lts_2024_seeding
branch
from
4d4bb82
to
f4d8b55
Compare
mwrock
changed the title
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.
THIS SHOULD NOT BE MERGED UNTIL BUILDER PACHAGES ARE AVAILABLE IN LTS-2024.
For LTS, we want to be able to validate that an on-prem instance does not have any core packages promoted to LTS that are not also LTS on public builder. So this PR introduces a tool to do this and give the user the option to demote any such packages. This tool will end up replacing the use of seed-lists.
For more complete documentation on the tool, see its README in the pkg-sync folder.
What this is missing is assistance for builder instances that have native package functionality disabled. These users must either upgrade to a newer builder where native packages are no longer feature flagged or they must configure their builders to enable native packages for the core origin.
Another enhancement to consider here is to add an arg for syncing a specific group of packages. Currently there is a commented arg for
--effortless-onlywhich will only fetch packages needed to use the effortless pattern. It is commented because those effortless packages are not yet in LTS. However, we will also have scenarios for just syncing habitat packages from stable or just getting builder packages for on-prem.