-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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 #10478
Comments
I started working on this, but too early to create a [WIP] PR. |
@janschumann any update on this? I'd be happy to help test as we're starting to look into using Chef Automate. |
Definitely would love any progress from you or any other contributors. Thanks all around! |
I mean there is https://github.com/johnbyrneio/chef-automate-terraform but it's likely to be unsupported longer term. |
@jpooler Yeah that's for standing up Chef Automate in AWS. I want to use the managed Chef Automate Service which handles node provisioning, backend storage durability, HA, upgrades, etc all for me. |
@janschumann Any updates? |
I have not been working on this since December. Had to focus on other things. Sorry for not responding to previous asking! |
Starting an implementation of this, should have something to demonstrate soon. |
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. |
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: