first step in migrating to registries.json #416
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
This was referenced Oct 23, 2024
k-rister
force-pushed
the
dev-kmr
branch
4 times, most recently
from
cc30bec to
db0fc0e
Compare
- create the registries.json JSON schema - add logic to bin/base to create a simple registries.json from the registry data that is loaded from /etc/sysconfig/crucible and verify that it passes schema validation - create a backup of /etc/sysconfig/crucible and then remove the legacy registry information from it - add logic to bin/base to load the data from registries.json into the existing environment variables that are used by Crucible and Rickshaw (a future change will allow Rickshaw to consume registries.json directly and migrate more config information to it) - capture registries.json as part of each run that is made - refactor bin/base so that things like container arguments are available when needed (to run the schema validator inside a podman container)
… the formal entry point rather than bypassing it
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.
create the registries.json JSON schema
add logic to bin/base to create a simple registries.json from the registry data that is loaded from /etc/sysconfig/crucible and verify that it passes schema validation
create a backup of /etc/sysconfig/crucible and then remove the legacy registry information from it
add logic to bin/base to load the data from registries.json into the existing environment variables that are used by Crucible and Rickshaw (a future change will allow Rickshaw to consume registries.json directly and migrate more config information to it)
capture registries.json as part of each run that is made
refactor bin/base so that things like container arguments are available when needed (to run the schema validator inside a podman container)