- Notifications
You must be signed in to change notification settings - Fork1k
fix(examples/templates/nomad-docker): ignoreNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomad#11341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
… coder's allocation.If coder is running the terraform CLI as a Nomad job, then it may be reading the NOMAD_NAMESPACE env var from that allocation.Added the ignore_env_vars to fix this problem.hashicorp/terraform-provider-nomad#386
github-actionsbot commentedDec 27, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
cdrcommunity added a commit to coder/cla that referenced this pull requestDec 27, 2023
Member
matifali commentedDec 27, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Hi,@FourLeafTec. Thanks for the PR. Does setting those environment variables to ignore condition solve the issue without the changes inhashicorp/terraform-provider-nomad#386? |
NOMAD_NAMESPACE andNOMAD_REGION env var when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION env var when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadmatifali approved these changesDec 27, 2023
NOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadNOMAD_NAMESPACE andNOMAD_REGION when Coder is running in nomadSign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
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.
If coder is running the terraform CLI as a Nomad job, then it may be reading the NOMAD_NAMESPACE env var from that allocation.
Added the ignore_env_vars to fix this problem.
hashicorp/terraform-provider-nomad#386