-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Aws Config Remediation #13884
Aws Config Remediation #13884
Conversation
Answering hashicorp#7972 This is my 1st go development ever, so please feel free to tell me if I did something in a bad way, which is most probable :) feat(go): learn pointers usage feat(config): parse all simple fields chore(naming): replace ConfigRule by RemediationConfiguration feat(config): add read flatten function feat(config): add delete function feat(config): use TypeSet instead of TypeList, & parse ResourceValue feat(config): parse StaticValue feat(config) flatten remediation config parameters to nil, just to get the function signature right feat(config): flatten remediation config parameters
chore(tidy): remove unused import comments test(config): copy-paste config rule test to start from something feat(test): add shredder feat(config): add a remediation configuration exemple feat(test): add getter check feat(config): add 1st finished acc test feat(test): remove unadapted commented tests & add a second true test feat(test): add static values tests chore(fmt): format the file with make fmt fixup! chore(fmt): format the file with make fmt fix(test): add required on fields chore(lint): proceed with linter results chore(lint): use correct configuration
0e58b74
to
f09dab2
Compare
f09dab2
to
b9d6c0c
Compare
Notification of Recent and Upcoming Changes to ContributionsThank you for this contribution! There have been a few recent development changes that affect this pull request. We apologize for the inconvenience, especially if there have been long review delays up until now. Please note that this is automated message from an unmonitored account. See the FAQ for additional information on the maintainer team and review prioritization. If you are unable to complete these updates, please leave a comment for the community and maintainers so someone can potentially continue the work. The maintainers will encourage other contributors to use the existing contribution as the base for additional changes as appropriate. Otherwise, contributions that do not receive updated code or comments from the original contributor may be closed in the future so the maintainers can focus on active items. For the most up to date information about Terraform AWS Provider development, see the Contributing Guide. Additional technical debt changes can be tracked with the As part of updating a pull request with these changes, the most current unit testing and linting will run. These may report issues that were not previously reported. Terraform 0.12 SyntaxReference: #8950 Version 3 and later of the Terraform AWS Provider, which all existing contributions would potentially be added, only supports Terraform 0.12 and later. Certain syntax elements of Terraform 0.11 and earlier show deprecation warnings during runs with Terraform 0.12. Documentation and test configurations, such as those including deprecated string interpolations ( Action Required: Terraform Plugin SDK Version 2Reference: #14551 The Terraform AWS Provider has been upgraded to the latest version of the Terraform Plugin SDK. Generally, most changes to contributions should only involve updating Go import paths in source code files. Please see the referenced issue for additional information. Action Required: Removal of website/aws.erb FileReference: #14712 Any changes to the Upcoming Change of Git Branch NamingReference: #14292 Development environments will need their upstream Git branch updated from Upcoming Change of GitHub OrganizationReference: #14715 This repository will be migrating from https://github.com/terraform-providers/terraform-provider-aws to https://github.com/hashicorp/terraform-provider-aws. No practitioner or developer action is anticipated and most GitHub functionality will automatically redirect to the new location. Go import paths including |
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.
Thanks, @cgetzen , this looks great! Thanks for picking up the PR
There are a couple minor changes to make, and we'd like to see a few more tests added to the acceptance tests.
}, | ||
}) | ||
} | ||
|
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.
We should also add tests for:
- changes that will update the rule in-place
- changes that will force a new resource
Terraform plugin SDK v2 Co-authored-by: Graham Davison <[email protected]>
Wrap AWS API error Co-authored-by: Graham Davison <[email protected]>
Remove double read Co-authored-by: Graham Davison <[email protected]>
Terraform Plugin SDK v2 Co-authored-by: Graham Davison <[email protected]>
resourceName Co-authored-by: Graham Davison <[email protected]>
…aform-provider-aws into f-aws_config_remediation
0c5bc38
to
57a4373
Compare
Hi @gdavison, thanks for the thorough review. I've made all the minor changes and added the acceptance tests "recreates", "updates", and "disappears".
|
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.
LGTM 🚀
Acceptance tests:
--- PASS: TestAccAWSConfig_serial/RemediationConfiguration (338.52s)
--- PASS: TestAccAWSConfig_serial/RemediationConfiguration/basic (81.33s)
--- PASS: TestAccAWSConfig_serial/RemediationConfiguration/disappears (77.77s)
--- PASS: TestAccAWSConfig_serial/RemediationConfiguration/recreates (91.55s)
--- PASS: TestAccAWSConfig_serial/RemediationConfiguration/updates (87.87s)
This has been released in version 3.7.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! |
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! |
Community Note
Closes #7972
Release note for CHANGELOG: