Allow Building Block Users to Trigger Upgrades Themselves
Janny the AI Product Manager
Problem / Use Case
When a new version of a Building Block is available, workspace users currently have to wait for the platform team to coordinate and trigger the upgrade. This creates scheduling overhead for platform teams and blocks users from getting the latest version on their own timeline.
Proposed Solution
Allow platform engineers to opt in (per Building Block Definition) to letting workspace users trigger a version upgrade themselves. This gives users self-service control over when they upgrade, while keeping platform teams in control of whether that option is available at all.
Andreas Grub
The idea of having another "policy" setting to allow self-service upgrades is sound, and we should also re-design how the "run_transparency" flag could be turned into something like "what is the BBD consumer/user (owning/ordering the BB) allowed to do". We should at least write down a list like:
* Allowed to trigger new runs (or also dry runs?)
* Allowed to see system logs
* Allowed to upgrade, allowed to dry run upgrade?
One might even extend this to allow approving certain situations.
All this must be discussed in view of the new BBD policies tab IMHO.
Andreas Grub
The idea of having another "policy" setting to allow self-service upgrades is sound, and we should also re-design how the "run_transparency" flag could be turned into something like "what is the BBD consumer/user (owning/ordering the BB) allowed to do". We should at least write down a list like:
* Allowed to trigger new runs (or also dry runs?)
* Allowed to see system logs
* Allowed to upgrade, allowed to dry run upgrade?
One might even extend this to allow approving certain situations.
All this must be discussed in view of the new BBD policies tab IMHO.