-
Notifications
You must be signed in to change notification settings - Fork 156
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
[TF-13376] Refactor registry module delete method #1267
[TF-13376] Refactor registry module delete method #1267
Conversation
b333f45
to
0c6472d
Compare
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.
Apologies, blocking following a pending discussion. ⬇️
2cca617
to
9e482a3
Compare
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.
Great work 👍
4614117
to
0a4c3df
Compare
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.
Almost there! Small issue with the error check ⬇️
0a4c3df
to
de58ded
Compare
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.
Apologies. I completely missed the !
.
Description
The Registry Module
Delete
API deprecated and replaced three endpoints (see docs). This ticket is a follow-on, after refactoring the API calls in go-tfe (PR) and releasing those changes in v1.45.0.Remember to:
Testing plan
Name
attr for both resources identicalProvider
attr for both resources differentExternal links
Include any links here that might be helpful for people reviewing your PR. If there are none, feel free to delete this section.
Output from acceptance tests
Please run applicable acceptance tests locally and include the output here. See testing.md to learn how to run acceptance tests.
If you are an external contributor, your contribution(s) will first be reviewed before running them against the project's CI pipeline.