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

make remote state initial behavior the same as local state #32614

Merged
merged 5 commits into from Feb 7, 2023

Commits on Feb 1, 2023

  1. Copy the full SHA
    09e0dff View commit details
    Browse the repository at this point in the history
  2. wip: refactored tests

    yardbirdsax committed Feb 1, 2023
    Copy the full SHA
    68e227d View commit details
    Browse the repository at this point in the history
  3. fix: remote state behavior

    This makes the behavior of remote state consistent with local state in regards to the initial serial number of the generated / pushed state. Previously remote state's initial push would have a serial number of 0, whereas local state had a serial of > 0. This causes issues with the logic around, for example, ensuring that a plan file cannot be applied if state is stale (see hashicorp#30670 for example).
    yardbirdsax committed Feb 1, 2023
    Copy the full SHA
    2576544 View commit details
    Browse the repository at this point in the history
  4. Copy the full SHA
    d45ebfb View commit details
    Browse the repository at this point in the history

Commits on Feb 7, 2023

  1. Update internal/states/remote/state.go

    Fix from review
    
    Co-authored-by: Nathan Mische <nmische@gmail.com>
    jbardin and nmische committed Feb 7, 2023
    Copy the full SHA
    2d9e3da View commit details
    Browse the repository at this point in the history