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

Add cidrs attribute to aws_lightsail_instance_public_ports resource #14905

Merged
merged 8 commits into from
Mar 25, 2021

Conversation

kurtmc
Copy link
Contributor

@kurtmc kurtmc commented Aug 29, 2020

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Release note for CHANGELOG:

Add cidrs attribute to aws_lightsail_instance_public_ports resource

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSLightsailInstancePublicPorts'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSLightsailInstancePublicPorts -timeout 180m
=== RUN   TestAccAWSLightsailInstancePublicPorts_basic
=== PAUSE TestAccAWSLightsailInstancePublicPorts_basic
=== RUN   TestAccAWSLightsailInstancePublicPorts_multiple
=== PAUSE TestAccAWSLightsailInstancePublicPorts_multiple
=== RUN   TestAccAWSLightsailInstancePublicPorts_cidrs
=== PAUSE TestAccAWSLightsailInstancePublicPorts_cidrs
=== CONT  TestAccAWSLightsailInstancePublicPorts_basic
=== CONT  TestAccAWSLightsailInstancePublicPorts_cidrs
=== CONT  TestAccAWSLightsailInstancePublicPorts_multiple
--- PASS: TestAccAWSLightsailInstancePublicPorts_cidrs (71.71s)
--- PASS: TestAccAWSLightsailInstancePublicPorts_multiple (74.38s)
--- PASS: TestAccAWSLightsailInstancePublicPorts_basic (93.91s)
PASS
ok      github.com/terraform-providers/terraform-provider-aws/aws       93.955s

@kurtmc kurtmc requested a review from a team August 29, 2020 04:10
@ghost ghost added size/XL Managed by automation to categorize the size of a PR. documentation Introduces or discusses updates to documentation. needs-triage Waiting for first response or review from a maintainer. provider Pertains to the provider itself, rather than any interaction with AWS. service/lightsail Issues and PRs that pertain to the lightsail service. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. labels Aug 29, 2020
@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch 3 times, most recently from 9a990ef to cda14d7 Compare August 29, 2020 04:18
@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch from cda14d7 to 6c93513 Compare December 15, 2020 05:12
@kurtmc kurtmc requested a review from a team as a code owner December 15, 2020 05:12
Base automatically changed from master to main January 23, 2021 00:58
@YakDriver YakDriver self-assigned this Mar 24, 2021
@YakDriver YakDriver removed the needs-triage Waiting for first response or review from a maintainer. label Mar 24, 2021
@YakDriver
Copy link
Member

@kurtmc Thank you for this PR! Some of this functionality will be merged as part of #8611. However, please consider rebasing and adding the additional attributes after that merges. Thank you!

@kurtmc
Copy link
Contributor Author

kurtmc commented Mar 24, 2021

@YakDriver Awesome! Thanks for the heads up.

@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch 2 times, most recently from da042d9 to c48dda4 Compare March 25, 2021 03:10
@ghost ghost added size/M Managed by automation to categorize the size of a PR. and removed size/XL Managed by automation to categorize the size of a PR. labels Mar 25, 2021
@kurtmc kurtmc changed the title Implement aws_lightsail_public_ports resource Add cidrs attribute to aws_lightsail_instance_public_ports resource Mar 25, 2021
@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch from c48dda4 to 2709720 Compare March 25, 2021 03:33
@kurtmc
Copy link
Contributor Author

kurtmc commented Mar 25, 2021

@YakDriver I have rebased now, and just added my cidrs attribute to the resource that exists in the main branch , but I am having trouble with the acceptance tests.

@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch from 2709720 to e0a9b73 Compare March 25, 2021 03:38
@kurtmc kurtmc force-pushed the feature/lightsail-public-ports branch from e0a9b73 to 690280e Compare March 25, 2021 04:01
Copy link
Member

@YakDriver YakDriver left a comment

Choose a reason for hiding this comment

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

Looks great! @kurtmc Thank you! 🎉

Acceptance tests on commercial:

--- PASS: TestAccAWSLightsailInstancePublicPorts_basic (44.70s)
--- PASS: TestAccAWSLightsailInstancePublicPorts_cidrs (55.74s)
--- PASS: TestAccAWSLightsailInstancePublicPorts_multiple (58.41s)

Acceptance tests on GovCloud:

--- SKIP: TestAccAWSLightsailInstancePublicPorts_basic (1.29s)
--- SKIP: TestAccAWSLightsailInstancePublicPorts_cidrs (1.29s)
--- SKIP: TestAccAWSLightsailInstancePublicPorts_multiple (1.29s)

@YakDriver
Copy link
Member

@kurtmc Rather than perform the sorts, I switched cidrs to type schema.TypeSet. It seems to work okay. I'm not 100% certain AWS will always provide the CIDRs in the same order so the acceptance test may flaky fail every now and then. I tried it many times in a row and always got the same order. The resource itself won't show diffs based on order since it is a set but since the test has a hardcoded index, there's the possibility of issues.

@YakDriver YakDriver added this to the v3.34.0 milestone Mar 25, 2021
@YakDriver YakDriver merged commit 69e0f43 into hashicorp:main Mar 25, 2021
@ghost
Copy link

ghost commented Mar 26, 2021

This has been released in version 3.34.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

@kurtmc kurtmc deleted the feature/lightsail-public-ports branch March 26, 2021 02:29
@ghost
Copy link

ghost commented Apr 24, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. provider Pertains to the provider itself, rather than any interaction with AWS. service/lightsail Issues and PRs that pertain to the lightsail service. size/M Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants