Feature request: Previewing Baseline updates prior to updating

[c9mb]

The portal Baseline Update process provides only a simple run or don't run choice, meaning it's very much a leap of faith that it's the right thing to do, and that the changes about to be applied to child sites are intended and safe.

A useful option would be the ability to preview the diff-list that will be applied to a child site, so an informed decision can be made before proceeding, and any corrections made before applying changes and potentially taking a child-site offline when an unintended change is made.

[nul800sebastiaan]

Hi @c9mbundy, we recommend you have a dev environment on your child site(s) so you can make sure everything works before you go live with it.

[c9mb]

Please note - Morten thought it a good idea and asked me to post it.
Please don't just dismiss it out of hand, as paying for a development environment on every child site, to avoid a problem that may have been easily picked up with a diff list of what you are about to push, seems a bit unreasonable.

[sitereactor]

Yeah not sure why this was closed 🤷‍♂️
Adding a development environment is certainly one why to preview changes in the Baseline child. But I understood this as a way to preview the changes that would be pushed from the Baseline master to child before actually pushing anything. So thought it would be a good idea to get this logged as a feature request. Maybe it wasn't obvious to Sebastiaan that this is a feature request.

[sitereactor]

I reopened this and added a few labels to indicate that its an idea / feature request.

[c9mb]

Cheers - I actually selected the feature-request template, but I'm guessing it doesn't make it clear.

[umbrabot]

Hiya @c9mbundy,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[c9mb]

@umbrabot still relevant

[sajumb]

@c9mbundy You are right. We will have some internal talks regarding this feature really soon.

[c9mb]

@sajumb Sounds good. This one is actually part of a pair of related requests-ideas - the other being #523 which is about listing and cherry-picking the pending commits on a baseline-master, so that patches and hot-fixes can be deployed without needing to deploy all pending commits to a baseline-child before they are ready to be released.

[miguelcrpinto]

Any updates/news on this topic?

[sajumb]

We currently do not have an update on this one. But we are conceptually working on various new features in Umbraco Cloud somehow related to this one, which we will share more insight about later this spring/early summer.