-
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
provider/aws: Fix spurious aws_spot_fleet_request diffs #12437
Conversation
Hi @Bowbaq Thanks for the work here - currently, this change breaks our acceptance tests due to the change of hash
I am going to try and fix this up before i can merge this Hope this is all ok - if so, stick with me for a day or 2 Paul |
Hi @Bowbaq I have fixed up the tests now and all looks good - I am going to manually merge this to get the commit for the test results in
Thanks for the work Paul |
@stack72 forgot to check the tests, my bad, thanks for fixing |
👍 |
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. |
This fixes the following issues:
launch_specification.monitoring
was""
, which got translated tofalse
by AWS, generating a spurious difflaunch_specification.ebs_optimized
was""
, which got translated tofalse
by AWS, generating a spurious difflaunch_specification.vpc_security_group_ids
were not read back from AWS, generating a spurious difflaunch_specification.vpc_security_group_ids
were not handled properly when setting 'associate_public_ip_address = true'launch_specification.user_data
was not handled consistently (sometimes hashed, sometimes not), generating a spurious diffI also cleaned up some dead code handling a
security_groups
property since there is no way for the user to define it.@stack72 it seems you've been reviewing spot fleet related PRs, so tagging you here.
One final note: it may be a good idea to reuse the same hash function for root/ebs/ephemeral volumes across this resource,
aws_instance
andaws_launch_configuration
?