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
The code should have executed without crashing during terraform plan operation
Actual Behavior
When:
terraform plan
is executed, the code causes Terraform to crash with panic.
Steps to Reproduce
Copy the terraform code above to a test file and run following commands in the same directory:
terraform init
terraform validate
terraform plan
Additional Context
Any invalid values in the resource properties were inserted as a part of cleaning logs.
The AD directory is shared from a different AWS account (via VPC peering and handshake) and was not created in this account. The executed users had admin privileges on DS, EC2 services in the destination account where the code was run.
All routing, security group and peering is working fine as well as aws cli:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Feb 19, 2021
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform Configuration Files
main.tf
Debug Output
Crash Output
Expected Behavior
The code should have executed without crashing during terraform plan operation
Actual Behavior
When:
is executed, the code causes Terraform to crash with panic.
Steps to Reproduce
Copy the terraform code above to a test file and run following commands in the same directory:
Additional Context
Any invalid values in the resource properties were inserted as a part of cleaning logs.
The AD directory is shared from a different AWS account (via VPC peering and handshake) and was not created in this account. The executed users had admin privileges on DS, EC2 services in the destination account where the code was run.
All routing, security group and peering is working fine as well as aws cli:
References
The text was updated successfully, but these errors were encountered: