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

Helper DRY method principle regarding AWS provider resources destroy (temporary DependencyViolation) #450

Closed
pmoust opened this issue Oct 18, 2014 · 3 comments

Comments

@pmoust
Copy link
Contributor

pmoust commented Oct 18, 2014

#436
#447
#448
#449

After merging those upstream perhaps it is time for us to consider introducing a helper callback method for this type of check on AWS provider to keep codebase DRY.

@mitchellh
Copy link
Contributor

Not a bad idea, at least for AWS. I think we should build a helper around DependencyViolation to start

@phinze
Copy link
Contributor

phinze commented Nov 17, 2015

I'm working on a sweep through old issues. This still seems like a valid clean-up thing to do, but w/ no activity in over a year I'm going to close this for now. We'd welcome any PRs along these lines. 👍

@phinze phinze closed this as completed Nov 17, 2015
@ghost
Copy link

ghost commented Apr 30, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants