-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New resource: aws_drs_replication_configuration_template
#26399
New resource: aws_drs_replication_configuration_template
#26399
Conversation
I had been using the git hub actions to fix formatting issues and one of them said to run #make gen and then commit. I did this and now there are merge conflicts due to the .semgrep-service-name.yml files since DRS is a new service. What is the proper path forward here? Revert that commit? |
Bump - would like to see this completed, could anyone detail what work remains? |
d2f8cb9
to
36d1f0c
Compare
aws_drs_replication_configuration_template
@k-brooks Thanks for your interest! Please see the op. |
aws_drs_replication_configuration_template
aws_drs_replication_configuration_template
a77d447
to
df1acae
Compare
Unfortunately, additional resources or functionality may be needed before this is useful. This is a best-effort first step. |
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.
Looks good to me!
This functionality has been released in v5.55.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. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #21865
Relates #37816
Output from acceptance testing:
Need assistance/guidance in creating an acceptance test for the new resource. I was hoping for some community help/support in creating the test.
Current Status (4 June 2024): ~90% there
@lewinkedrs Thank you for your work on this! I have reworked your PR significantly so make sure to pull your branch if you happen to work on it again.
Invalid request body
)