Export: Allow deleting manifests of specific envs when merging exports #871
Conversation
This file contains 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
If, for example, `env1` and `env2` were deployed. `env2` is renamed to `env3`, the "merge" export would only export env3, causing manifest conflicts because `env2` manifests were removed The feature is explained more in-depth in the docs changes
julienduchesne
force-pushed
the
julienduchesne/deleted-envs
branch
from
f758b2f
to
da2c7ff
Compare
|
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.
If, for example,
env1andenv2were deployed andenv2was renamed toenv3, the "merge" export would only exportenv3, causing manifest conflicts becauseenv2manifests were not removedThe feature is explained more in-depth in the docs changes