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

Refresh fails if partially complete state with outputs that depend on bad resources #483

Closed
mitchellh opened this issue Oct 20, 2014 · 3 comments

Comments

@mitchellh
Copy link
Contributor

If we have a partial state in a configuration with outputs that use resources that didn't complete, then refresh/apply won't run.

@mitchellh
Copy link
Contributor Author

This is more annoying than I thought. The count can be dynamic, so we can't actually ever be sure that we have everything we need to satisfy the outputs. i.e. if we have value = "${aws_instance.foo.5.id}" but there are only 3 of aws_instance.foo, we can't really know that at refresh time.

@mitchellh
Copy link
Contributor Author

For refresh, I think we ignore dependency errors. If they come up at plan/apply time, then the user can handle it. We really just need to not block refresh.

@mitchellh
Copy link
Contributor Author

Fixed.

phinze added a commit that referenced this issue Mar 11, 2016
Prevents residual script contents from remaining on machine.

Fixes #483
@ghost ghost locked and limited conversation to collaborators May 5, 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

1 participant