fix: add customizable final_snapshot_identifier #104
Closed
+8
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @osterman, could you review this? |
to be able to have multiple db apply/destroy lifecycles in the same account
kaiehrhardt
force-pushed
the
add-final_snapshot_identifier
branch
from
bd4af31 to
9d70697
Compare
|
💥 This pull request now has conflicts. Could you fix it @kaiehrhardt? 🙏 |
|
This PR was closed due to inactivity and merge conflicts. 😭 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
add customizable final_snapshot_identifier
why
to be able to have multiple db apply/destroy lifecycles in the same account