This repository was archived by the owner on Jun 27, 2025. It is now read-only.
Add support for deploying a pre-rendered jobspec. #445
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
…ith nomad/HCL2 but still make use of levant's deployment watcher.
|
|
use deployment watcher if deploy id exists
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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 adds the -pre-rendered flag to levant deploy, so it can accept a pre-rendered jobspec from nomad/HCL2.
Render separately with nomad/HCL2 but still make use of levant's deployment watcher. See example in commands doc.
This is to address issue #444
I'm wondering if there are caveats I may be missing...
Pulling apart rendering from deployment means several rendering-specifc deploy command options don't apply (no vars or consul), but a lot of them still do, such as -force-count.