You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
If we have a partial state in a configuration with outputs that use resources that didn't complete, then refresh/apply won't run.
The text was updated successfully, but these errors were encountered: