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

core: New Refresh Graph #11341

Closed
wants to merge 4 commits into from
Closed

core: New Refresh Graph #11341

wants to merge 4 commits into from

Conversation

mitchellh
Copy link
Contributor

@mitchellh mitchellh commented Jan 22, 2017

This PR modifies the refresh graph to use a new custom graph builder. This work is just continuing the work I started and shipped for 0.8 but on the less complex and less dangerous graphs. See #9973 or #9388 as prior examples.

The goal at this point now that plan/apply have shipped on new graphs is to complete the less dangerous graphs so we can ultimately fully remove the legacy graph building code. We still have to do refresh, validate, and input.

The changes here are minimal since refresh is simple. What this PR changes/adds:

  • New refresh graph, based on state as primary source of truth
  • StateFilter made more robust to handle cases where state may not have resource type. This was necessary for tests to pass without changes.
  • ConfigTransformer can filter the types of things added. This was necessary to add only data sources for refresh.

This PR does not enable/use the shadow graph. Refresh is not a scary operation (compared to plan/apply) and therefore we won't be using the shadow graph for this. We'll be shipping in default-on in 0.9 betas and let any bugs come through there.

This was possible with test fixtures but it is also conceiably possible
with older states or corrupted states. We can also extract the type from
the key so we do that now so that StateFilter is more robust.
@mitchellh
Copy link
Contributor Author

Closing for #11426 which builds on top of this.

@mitchellh mitchellh closed this Jan 26, 2017
@grubernaut grubernaut deleted the f-new-refresh branch May 11, 2017 00:31
@ghost
Copy link

ghost commented Apr 12, 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 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants