allowing templates to be applied AFTER the cluster is fully up #181
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
mddamato
requested changes
Jan 16, 2024
mddamato
approved these changes
Jan 16, 2024
aleiner
deleted the
180-allow-for-manifests-to-be-applied-after-the-cluster-is-fully-up
branch
|
How is this different than the |
|
@jcox10 - Thanks for keeping us honest. PR has been submitted to address the additional documentation. We will rework some of the logic before a new release where the variable names may change to make things more streamlined. |
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.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
(REQUIRED)
Allows for manifest files to be applied after the cluster is up. Current functionality only allows for manifests to be applied after the first server node is up.
Which issue(s) this PR fixes:
(REQUIRED)
Fixes #180