-
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
r/elasticsearch_domain - tag on create + refactor to use waiter and finder packages #18082
r/elasticsearch_domain - tag on create + refactor to use waiter and finder packages #18082
Conversation
ec81be8
to
5cd3f9e
Compare
72a31fa
to
8ce4010
Compare
Just checking when this MR will be merged. We are waiting for this feature |
Seconded we are also waiting on this |
8ce4010
to
6c7545a
Compare
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
Hi @DrFaust92 👋 do you mind fixing up the merge conflicts that came up after the service packages refactor when you have a moment? |
20dfff9
to
8dd0eaa
Compare
@anGie44 rebased + more fixes but didnt get to run all tests yet. |
thank you @DrFaust92 ! No worries about running the tests, I can do so on my end 👍 |
@anGie44 i see something else was merged and now it created a conflict. would like me to rebase and try to take care of it or you will look into it? |
Hey @DrFaust92 -- apologies for not getting back to this sooner and the merge conflicts! i'll have a look and rebase |
5f768b8
to
38c761b
Compare
38c761b
to
6be0e46
Compare
77db51f
to
c9fd1c3
Compare
Hi again @DrFaust92 -- so i rebased and merged back in the changes from https://github.com/hashicorp/terraform-provider-aws/pull/22157/files#diff-06ff9b94aba8bd561ec9bbcca77f52542eb0bc702f2b43c5c73f8a467797bd95 which added the new function |
@anGie44 i dont recall atm why i did it but i do remember failures around that test (and others) in regards to |
Thanks @DrFaust92 -- i think for the scope of this PR, I would just recommend removing the test config additions:
and then add a changelog entry and we should be good to go 👍 |
Output of acceptance tests (commercial):
|
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.
@DrFaust92 , i've reverted the test config back to the state of main
and everything's passing again with the refactor changes. Thanks again for these changes!
This functionality has been released in v3.71.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 #20544
Output from acceptance testing: