chore(release): 2.0.0#39
Merged
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
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.
Summary
2.0.0 reworks the configuration surface into something simpler to write and harder to get wrong, and brings a set of improvements for standalone hosts. Settings group into per-concern structs, every default lives in the module and merges deep across Hiera layers so node data holds only its deviations, and the values the module can derive for itself (file ownership, socket paths,
DOCKER_HOST) are no longer parameters to set, for simplicity. A shipped Hiera data check validates consumer data against the declared parameter surface and fails loud on an unknown key. Standalone hosts gain a self-contained runbook, a liveness healthcheck decoupled from the self-update loop, and enforced subordinate-ID widths sized for nested builds with rootless BuildKit. It is a breaking change: node data written for 1.x must be migrated.Changes
Unreleasedchangelog section to2.0.0and open a freshUnreleased.metadata.jsonto2.0.0.runner_tokensreference in the README prose.The feature work released here already landed on
mainthrough earlier merges; see the CHANGELOG for the complete list.Breaking changes and migration
2.0.0 is a major version upgrade. Node data must be rewritten from the flat parameters to the grouped structs (
runner_account,configuration_file,packageswith itssources,rootless_docker,runner_service, andstandalonewith the nestedself_update). Rename thetokenskey torunner_tokensin both host data and the secret store file. Several 1.x parameters are gone because the module now derives or fixes their values; the Removed section of the CHANGELOG lists them. Because a mistyped subkey now fails the compile rather than being ignored, the first apply on migrated data surfaces any leftover 1.x keys immediately.Verification
just checkgreen (validate, lint, docs).