Metadata Manifest and Promotion Manager Questions

Nextworld Platform
1
  1. What is the row/form action called “Close Action” on the Promotion Manager?
  2. When I get a failure on promotion manager:
    a. Is there a way to link to the validation workbench?
    b. I re-ran the promotion and the status didn’t go from “Failed” to “Rerunning” or something. It stayed at “Failed.” So when it failed again, I missed it in the UI - I had to catch it in jobs.
  3. Would it be possible for the metadata manifest to validate if the same number of objects on the LC are also the ones that got pulled into the manifest? I think this would help us ensure everything is getting moved over.
  4. Are you all working on a way to inform users if objects have been updated in a recent manifest / promoted recently? (Not sure the time frame) This would prevent overrides of data.
2
  1. The ‘Close’ action’ button puts that promotion action into a closed state which prevents you from running further promotions against it. You can re-open the promotion action if needed once it is in a closed state
  2. Failures in promotion manager:
    1. If validation errors occur when running the promotion they are made visible via an inline app that is under the ‘Validation Rule Violations’ tab for the promotion action run that failed. You can see all the rule violations there. If for some reason you wanted to go to the actual Validation Workbench to see the errors you can copy the run Id and filter by it. The same information is displayed in the inline app and Validation Workbench
    2. The individual promotion action runs (visible when you go into the detail of your promotion action) report their running state. It’s possible we are not updating the main promotion state accordingly. Could you file a bug for us to investigate?
  3. When you run the ‘prepare manifest’ action for a manifest that is a ‘merge request’ type it should be automatically grabbing the objects specified in each of the specified merge requests/branch lifecycles
  4. Multiple promotions that try to move the same objects into the same target can step on each other. The most recent will override. We don’t have any safeguards against this other than the user being careful and aware of what they are moving during the patching/hot patching process.
4 Likes
3

Thanks, Ben! That was really helpful. I will make a bug for the main promotion state to get updated. For #3, there have been a few times an object was not moved over so that is why I wanted a validation. For #4, could we put an idea in so that there is less reliance on the user?