-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider/aws: Support OpsWorks ECS Layers #182
Comments
+1 for this feature. Thanks! |
Any updates on this topic? |
Any updates? |
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! |
This functionality has been released in v4.3.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
This issue was originally opened by @eedwardsdisco as hashicorp/terraform#7036. It was migrated here as part of the provider split. The original body of the issue is below.
Request for support of OpsWorks ECS Layer Type, including the ability to associate an ECS Cluster with an OpsWorks ECS Layer.
http://docs.aws.amazon.com/opsworks/latest/userguide/workinglayers-ecscluster.html
The text was updated successfully, but these errors were encountered: