provider/aws: Use a endpoint where a stack lives for all opsworks resources

[hashibot]

This issue was originally opened by @nabeken as hashicorp/terraform#13483. It was migrated here as part of the provider split. The original body of the issue is below.

---

I open a new issue because it's a case which described in hashicorp/terraform#13024 (comment)

Terraform Version

Probably 0.9.2

Affected Resource(s)

• resource_aws_opsworks_application
• resource_aws_opsworks_custom_layer
• resource_aws_opsworks_ganglia_layer
• resource_aws_opsworks_haproxy_layer
• resource_aws_opsworks_instance
• resource_aws_opsworks_java_app_layer
• resource_aws_opsworks_memcached_layer
• resource_aws_opsworks_mysql_layer
• resource_aws_opsworks_nodejs_app_layer
• resource_aws_opsworks_permission
• resource_aws_opsworks_php_app_layer
• resource_aws_opsworks_rails_app_layer
• resource_aws_opsworks_rds_db_instance
• resource_aws_opsworks_static_web_layer
• resource_aws_opsworks_user_profile

It looks like resource_aws_opsworks_stack has been patched in 0.9.2.

Expected Behavior

Except resource_aws_opsworks_stack resources should go to a endpoint where a stack lives too.

Actual Behavior

Only resource_aws_opsworks_stack go to a endpoint where it lives.

References

• provider/aws: Fix issue upgrading to Terraform v0.9+ with AWS OpsWorks Stacks terraform#13024 (comment)
• Terraform 0.9.x "forgot" about OpsWorks resources terraform#12842

[steve-dave]

@catsby is this fix far from being released? just trying to establish if we need to find a workaround... 😄

[jdirwin]

Friendly reminder: us Opsworks users are stuck on Terraform 0.8.8 due to this bug.

[dav009]

@jdirwin any updates on this, I saw you closed your fork. I am working on a fix addressing other issues, but I wonder if you managed to get around this.

Cheers

[dav009]

To anyone stuck on this, one way to go around this is to: https://www.terraform.io/docs/configuration/providers.html

add a provider in us-east-1

provider "aws" {
  alias  = "america"
  region = "us-east-1"
}

on your opsworks layers, opsworks instances , opsworks custom layers etc...

resource "aws_opsworks_instance" "abcdef" {
  provider = "aws.america"
  ...
  ...
}

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!