Support Autoloading of Default Files #10
Comments
ygersie
pushed a commit
to ygersie/levant
that referenced
this issue
Nov 15, 2017
A basic way of implementing issue hashicorp#10 If no argument is given we check for the existence of a levant.nomad jobfile. If no -var-file is given we check for the existence of a levant.tf variable file. This "standardizes" the use of named files and makes pipelines clean in command usage.
Merged
ygersie
pushed a commit
to ygersie/levant
that referenced
this issue
Nov 16, 2017
A basic way of implementing issue hashicorp#10 If no argument is given we check for the existence of a levant.nomad jobfile. If no -var-file is given we check for the existence of a levant.tf variable file. This "standardizes" the use of named files and makes pipelines clean in command usage.
ygersie
pushed a commit
to ygersie/levant
that referenced
this issue
Dec 12, 2017
A basic way of implementing issue hashicorp#10 If no argument is given we check for the existence of a levant.nomad jobfile. If no -var-file is given we check for the existence of a levant.tf variable file. This "standardizes" the use of named files and makes pipelines clean in command usage.
jrasell
added a commit
that referenced
this issue
Dec 15, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
It would be cool if Levant supported autoloading of default files when running
levant deploy.Proposal
When a user runs
levant deploy, Levant would look in the directory for a default variable filelevant.yaml|hcl|ymland if a single Nomad job file is present, would use the default variable file to render any parameterized sections and trigger a deployment.This would be similar to the behavior of Terraform where a
terraform.tfvarsfile is automatically referenced and any*.tffile is processed. For this use case, it would probably make sense to only support this feature if a single*.nomadfile is present.The text was updated successfully, but these errors were encountered: