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: Add agent_version argument to AWS_OPSWORKS_STACK #6493

Merged
merged 1 commit into from
May 5, 2016

Conversation

u2mejc
Copy link
Contributor

@u2mejc u2mejc commented May 5, 2016

This PR adds the omitted OpsWorks Agent version, used when creating Opsworks stacks.

agent_version is supported in AWS_OPSWORKS_INSTANCE, but AWS's api limits you to "INHERIT" or a static version number. The API default is to statically set the current version. Adding the agent_version argument to aws_opsworks_stack allows specifying "LATEST" so that the client can be automatically updated to the latest version.

@@ -37,6 +37,7 @@ The following arguments are supported:
* `service_role_arn` - (Required) The ARN of an IAM role that the OpsWorks service will act as.
* `default_instance_profile_arn` - (Required) The ARN of an IAM Instance Profile that created instances
will have by default.
* `agent_version` - (Optional) If set to `"LATEST"`, OpsWorks will automatically install the latest version.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is Latest the only accepted option?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Paul!

The SDK also allows you to pass specific version numbers there too, but that feature is already exposed at the instance level. The stack being the parent of the instance, will set the instance version by default. The reason for the PR is that automatic updates are not allowed at the instance level (and it's not a default).

You can find supported versions for your stack from the cli:

$ aws opsworks describe-agent-versions --stack-id ***************************************

{
    "AgentVersions": [
        {
            "Version": "3421-20150611173115",
            "ConfigurationManager": {
                "Version": "11.10",
                "Name": "Chef"
            }
        },
        {
            "Version": "3422-20150629124612",
            "ConfigurationManager": {
                "Version": "11.10",
                "Name": "Chef"
            }
        },
        {
            "Version": "3424-20150709092700",
            "ConfigurationManager": {
                "Version": "11.10",
                "Name": "Chef"
            }
        },

~ Justin 🍻

@stack72
Copy link
Contributor

stack72 commented May 5, 2016

Hi @u2mejc

Just left a small question about the options of agent_version

P.

@stack72
Copy link
Contributor

stack72 commented May 5, 2016

What you've said makes sense :) this LGTM!

@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

Successfully merging this pull request may close these issues.

2 participants