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

Add pre and post upgrade step validation feature to extensions API #31

Open
fabiocarvalho777 opened this issue Nov 3, 2017 · 0 comments

Comments

@fabiocarvalho777
Copy link
Member

There should be a pre and a post upgrade step validation, as part of the extensions API.

The pre validation will happen right before each upgrade step, and the post validation will happen right after each upgrade step.

Requirements:

  1. Pre-validation: checks if the application is eligible to go through the upgrade step, and fails the transformation if the application is not in a valid state
  2. Post-validation: checks if the application is in a valid and acceptable state after the upgrade step transformation. Depending on the validation criteria (which is defined by the extension) the upgrade can proceed to the next upgrade step or fail the whole upgrade, even after all transformation operations have been already performed.
  3. Upgrade step validations API is part of Extensions API
  4. Upgrade step pre and post validations can be turned ON or OFF
  5. Upgrade step pre and post validations should be able to run TUs
  6. Upgrade step pre and post validations must not be able to run TOs, or modify the app in any ways (except post-transformation manual instructions)
  7. Upgrade step post validations can be used to gather meta-data about the transformed application and produce one ore more post-transformation manual instruction, depending on the state of the transformed application.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant