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

provider/aws: Support Windows OpsWorks Stacks #5569

Closed
EEDARIT opened this issue Mar 10, 2016 · 5 comments
Closed

provider/aws: Support Windows OpsWorks Stacks #5569

EEDARIT opened this issue Mar 10, 2016 · 5 comments

Comments

@EEDARIT
Copy link

EEDARIT commented Mar 10, 2016

Trying to create an AWS_OPSWORKS_STACK with "default_OS" set to "Microsoft Windows Server 2012 R2 Base" returns:

* aws_opsworks_stack.test: ValidationException: Configuration Manager: can't be changed from Chef::11.4 to Chef::12.2, must be Chef::0.9

OpsWorks Windows stacks need to be created with Chef 12.2 (info) and you can't change a Linux stack to a Windows stack once it has been created (info).

Looking at the OpsWorks Go file it appears that it is creating a default stack first, which is Linux, and then trying to update the other settings once the stack is created. Since you can't change a Linux stack to a Windows stack, this implementation won't work as far as I understand it.

@phinze
Copy link
Contributor

phinze commented Mar 10, 2016

Thanks for the report @EEDARIT 👍

Marked tentatively as a bug and pinging @apparentlymart, who I believe is our resident OpsWorker 😀

@apparentlymart
Copy link
Contributor

Yeah, this definitely looks like a bug. As you said @EEDARIT, it's erroneously trying to transform the stack from Linux to Windows.

The implementation here is trying to make a minimal stack in Create and then update it in Update in order to reduce code duplication, but in retrospect it'd be better to find a way to refactor this a bit so that it can just create stuff the right way to begin with. This is complicated by the fact that CreateStackInput and UpdateStackInput are not the same type, so it's difficult to write this generically in Go.

@phinze
Copy link
Contributor

phinze commented Mar 21, 2016

The fix in #5724 looked simple enough to pull in as is while we work on a larger fix. Seems reasonable to add DefaultOs on the initial create if that fixes up the windows code path. Will leave this open to continue discuss amore holistic fix.

@stack72
Copy link
Contributor

stack72 commented Apr 19, 2016

Closed in #6244

@stack72 stack72 closed this as completed Apr 19, 2016
@ghost
Copy link

ghost commented Apr 26, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants