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.

Sign up for GitHub

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

Jump to bottom

core: Do not persist state after plans #6811

Merged
merged 2 commits into from
May 24, 2016
Merged

core: Do not persist state after plans #6811

merged 2 commits into from
May 24, 2016

Commits on May 23, 2016

  1. core: Do not persist state after plans 

    This makes the behavior of plans much more predictable, as they no
longer potentially have side effects on shared remote state.
    @phinze
    phinze committed May 23, 2016
    Configuration menu
    Copy the full SHA
    ae73aa2 View commit details
    Browse the repository at this point in the history

Commits on May 24, 2016

  1. core: Make refresh message explicitly point out lack of state persist 

    Helps make clear to users that refresh only occurs in-memory during plan

per @jen20's recommendation
    @phinze
    phinze committed May 24, 2016
    Configuration menu
    Copy the full SHA
    aee1520 View commit details
    Browse the repository at this point in the history