Skip to content
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

Closed
hashibot opened this issue Jun 13, 2017 · 5 comments
Closed

[Feature Request] OpsWorks for Chef Automate Support #403

hashibot opened this issue Jun 13, 2017 · 5 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/opsworks Issues and PRs that pertain to the opsworks service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@hashibot
Copy link

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 :)

@hashibot hashibot added the enhancement Requests to existing resources that expand the functionality or scope. label Jun 13, 2017
@radeksimko radeksimko added the service/opsworks Issues and PRs that pertain to the opsworks service. label Jan 25, 2018
@mobileatjds
Copy link

We would like this as well!

@yves-vogl
Copy link

He guys, what's the status on this?

@zeusttu
Copy link

zeusttu commented Feb 25, 2020

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.

@github-actions
Copy link

github-actions bot commented Feb 1, 2023

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!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Feb 1, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
@github-actions
Copy link

github-actions bot commented Apr 4, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/opsworks Issues and PRs that pertain to the opsworks service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants