You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd into cdktf.out/stacks/test and run terraform init manually
Anything Else?
For additional context, the requirement I am trying to satisfy is supporting an air gapped install. Reaching out to registry.terraform.io is not possible from the target environment and a plan can't be done outside of the target environment. I am looking for the best solution to eliminate the last step that is indicated as follows
test - Fetching hashicorp/aws 5.49.0 for linux_amd64...
test - Retrieved hashicorp/aws 5.49.0 for linux_amd64 (signed by HashiCorp)
- Obtained hashicorp/aws checksums for linux_amd64; Additional checksums for this platform are now tracked in the lock file
interestingly, if I run cdktf diff test && cd cdktf.out/stacks/test && terraform init I don't see terraform reaching out to do this retrieve and the .terraform.lock.hcl file only contains what is in my local mirror. What is cdktf doing differently?
# This file is maintained automatically by "terraform init".
# Manual edits may be lost in future updates.
provider "registry.terraform.io/hashicorp/aws" {
version = "5.49.0"
constraints = "5.49.0"
hashes = [
"h1:Y3xvYjzBIwYSbcnZDcs6moiy30uxRoY5oT2ExQHKG5A=",
]
}
References
No response
Help Wanted
I'm interested in contributing a fix myself
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Expected Behavior
.terraform.lock.hcl contains only hashes that are in the local mirror and does not reach out to registry.terraform.io
Actual Behavior
.terraform.lock.hcl contains all available hashes for used providers and reaches out to registry.terraform.io
Steps to Reproduce
you'll see all hashes are here vs just the ones configured in the mirror
Versions
language: typescript
cdktf-cli: 0.20.0
node: 20.11.1
cdktf: 0.20.0
terraform: 1.8.0
arch: x86_64
os: RHEL UBI 8 (docker)
Providers
│ Provider Name │ Provider Version │ CDKTF │ Constraint │ Package Name │ Package Version │
│ aws │ 5.44.0 │ ^0.20.0 │ │ @cdktf/provider-aws │ 19.0.0 │
Gist
https://github.com/jej2003/sample_cdktf/blob/main/output.log
Possible Solutions
No response
Workarounds
cd into cdktf.out/stacks/test and run terraform init manually
Anything Else?
For additional context, the requirement I am trying to satisfy is supporting an air gapped install. Reaching out to registry.terraform.io is not possible from the target environment and a plan can't be done outside of the target environment. I am looking for the best solution to eliminate the last step that is indicated as follows
interestingly, if I run
cdktf diff test && cd cdktf.out/stacks/test && terraform init
I don't see terraform reaching out to do this retrieve and the .terraform.lock.hcl file only contains what is in my local mirror. What is cdktf doing differently?References
No response
Help Wanted
Community Note
The text was updated successfully, but these errors were encountered: