-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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 Elastic Beanstalk option settings with optional parameters #6476
Comments
Hello @dharrisio, |
@WolfHazardous I should be able to get to this sometime this week. |
Hi, Waiting the implementation I've used a provisioner on the environment resource to achieve what I need. provisioner "local-exec" {
command = "aws elasticbeanstalk update-environment --environment-id ${aws_elastic_beanstalk_environment.env.id} --cli-input-json file://${path.root}/beanstalk-update-env.json"
} And the file beanstalk-options.json contains the required option with ResourceName : {
"OptionSettings": [
{
"ResourceName": "downweeknight",
"Namespace": "aws:autoscaling:scheduledaction",
"OptionName": "MinSize",
"Value": "0"
}... As soon as the implementation will be publicly available I'll replace the hack :) Cheers |
Closed via #7376 |
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. |
In Elastic Beanstalk the aws:autoscaling:scheduledaction option settings require an additional parameter. After glancing through all the option settings, it looks like this is currently the only set of settings requiring more than namespace, name and value.
[http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-autoscalingscheduledaction]
Thanks to @rurreac for bringing this issue up in #3157. I created this issue to track it separately from the old, closed issue.
The fix for this looks fairly simple, as we may simply need to add an optional parameter in the setting schema. The hashing functions would also need to update to use the
resource_name
parameter in the hash when it is specified.The text was updated successfully, but these errors were encountered: