-
Notifications
You must be signed in to change notification settings - Fork 1
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
Dry-run and validate synchronisation plan #9
Labels
kind/enhancement
Categorizes issue or PR as related to an improvement.
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
Milestone
Comments
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Apr 21, 2024
csatib02
added
kind/enhancement
Categorizes issue or PR as related to an improvement.
and removed
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
labels
Apr 21, 2024
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
label
Aug 11, 2024
csatib02
added
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
and removed
lifecycle/stale
Denotes an issue or PR that has become stale and will be auto-closed.
labels
Aug 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/enhancement
Categorizes issue or PR as related to an improvement.
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
Goal
Currently, there is no way to tell if the given sync plan is valid or not. We would like to be able to notify user about plan validity.
This can be done through:
The text was updated successfully, but these errors were encountered: