-
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
added placement group as an option for autoscaling groups #3704
Conversation
Elem: &schema.Schema{Type: schema.TypeString}, | ||
Set: schema.HashString, | ||
}, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just think the addition to the schema should be really simple:
TypeString
Optional
This goes as per the fact the docs says that the input is a string and can be empty
@stack72 thanks for all the help! I've caught up with your suggestions and updated my branch. |
@dayer4b, this looks much better I just ran your tests and got the following:
In order to fix these (verified), you need to make the test config as follows:
Notice that the test now sets up Paul |
oh, of course. that makes a lot of sense. sorry. I'll get on that |
Just an update - I added the |
thanks @dayer4b - I will give your tests a shot again :) |
@dayer4b ok, I re-pulled your PR and the basic test actually doesn't work. Currently, your test config looks as follows:
This results in a test error as follows:
Your config needs to look as follows:
You only added the placement_group resource to the documentation |
wow, i had made the change and left it unstaged. sorry. i just pushed. |
are there any remaining issues with this? I can amend my branch if need be |
@dayer4b ok, so I've just re-tested this and have some final recommendations (I promise!)
then at the bottom of the test class you can add the config:
This then makes the test pass! |
added placement group as an option for autoscaling groups
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 reference to issue #3703