-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Feature Request] OpsWorks for Chef Automate Support #403
Comments
We would like this as well! |
He guys, what's the status on this? |
It is in fact possible to create an OpsWorks server with Terraform by embedding a CloudFormation stack which creates the server. It's hacky, but looks like an acceptable workaround to me until the linked PR gets finished and merged. |
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! |
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#10478. It was migrated here as part of the provider split. The original body of the issue is below.
Just announced at re:Invent 2016
https://www.chef.io/opsworks/
OpsWorks now supports Chef Automate (a managed chef server... woo!)
This is a feature request to add support for the new opsworks service to Terraform :)
The text was updated successfully, but these errors were encountered: