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
This issue arrises from a question on the mailing list (see here). Here, it was confirmed that this is a bug, thus this issue.
The problem is that OpsWorks resources cannot be imported from anywhere other than us-east-1. The reason for this is that the OpsWorks client is hard-coded to connect to us-east-1 here. The assumption that OpsWorks is only supported in us-east-1 was true until recently. It is now incorrect.
One possible solution is to remove the restriction of the OpsWorks client to us-east-1.
Terraform Version
Terraform v0.7.8
Affected Resource(s)
I have confirmed that the issue affects:
aws_opsworks_stack
aws_opsworks_custom_layer
However, it's likely that this affects all OpsWorks resources.
I edited the file mentioned in blooshirt's reporting of the bug and compiled in debug mode. I was able to successfully run terraform import was_opsworks_stack for zone us-west-1.
Unfortunately when I tried to run the tests they failed, so I couldn't issue a pull request.
What I did:
this is line 285
client.opsworksconn = opsworks.New(usEast1Sess)
I changed it to
client.opsworksconn = opsworks.New(less)
So it uses the region passed in by the command line
I don't know go, so if I get ambitious I may try and fix the tests and issue a pull request.
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 and limited conversation to collaborators
Apr 15, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue arrises from a question on the mailing list (see here). Here, it was confirmed that this is a bug, thus this issue.
The problem is that OpsWorks resources cannot be imported from anywhere other than us-east-1. The reason for this is that the OpsWorks client is hard-coded to connect to us-east-1 here. The assumption that OpsWorks is only supported in us-east-1 was true until recently. It is now incorrect.
One possible solution is to remove the restriction of the OpsWorks client to us-east-1.
Terraform Version
Terraform v0.7.8
Affected Resource(s)
I have confirmed that the issue affects:
However, it's likely that this affects all OpsWorks resources.
Terraform Configuration Files
None necessary
Debug Output
https://gist.github.com/blooshirt/269a2152eac887b2e66f11a787211926
Expected Behavior
Terraform should import the OpsWorks stack with the given ID.
Actual Behavior
Terraform fails with an error indicating that the stack cannot be found.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: