Add funcitonality for Linux Configuration-Targets#2
Merged
Conversation
Flux needs a container service. Normally, it will be configured to talk to an external container service (e.g., a K8s cluster), but, if we're installing to a target for which a user will use a local container service (e.g., podman or docker), we want to ensure that the container-service is available for flux to talk to
While we're here: - Trim extraneous "}"s
...Doing this helps expose and gaps in explicit state-ordering
Also nuke out the staged install-archive if it's somehow still present
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
1 participant
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.
Adds installation, configuration and "clean" automation for (enterprise) Linux configuration-targets.