Adding more info to Fusion upgrade - #9762
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
runleonarun
left a comment
There was a problem hiding this comment.
I love this change but am a little confused.
| - You must have the <Constant name="Fusion" /> beta enabled for your account. For more information, please contact your account manager. | ||
| - You must have the proper [permissions set](/docs/platform/manage-access/enterprise-permissions) to access all of the upgrade features: | ||
|
|
||
| | Feature | Required permission(s) | Permission sets with access | |
There was a problem hiding this comment.
For the "Permission sets with access" column, does it mean that
only Admins and Account Amins can perform upgrade? Or do different roles perform upgrades for different "features?"
| - Your dbt project must be updated to use the **Latest** release track. | ||
| - You must have a `developer` license. | ||
| - You must have the <Constant name="Fusion" /> beta enabled for your account. For more information, please contact your account manager. | ||
| - You must have the proper [permissions set](/docs/platform/manage-access/enterprise-permissions) to access all of the upgrade features: |
There was a problem hiding this comment.
I only see two roles that can access all of these. Should we state that each upgrade task can be performed by different people? Or one person with all of these permission sets?
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
runleonarun
left a comment
There was a problem hiding this comment.
So much clearer thank you!
| |---------|------------------------|-----------------------------| | ||
| | Enable Fusion access (triggers migration flows) | Fusion readiness: `write` <br></br> Projects: `write` | Admin, Account Admin and anyone assigned the Fusion admin set, provided their base role also has `write` access to projects | | ||
| | View Fusion readiness and job eligibility | Fusion readiness: `read` | Developer, Admin, Member, Account Admin, Fusion admin | | ||
| | "Run once on Fusion" | Runs: `write` | Job Admin, Job Runner, Admin, Member, Project Creator, Account Admin | |
There was a problem hiding this comment.
Why is this upgrade task quoted?
There was a problem hiding this comment.
It was for the button action, fixed it to match style guide
What are you changing in this pull request and why?
Adds a table that defines the permissions required for each of the Fusion upgrade workflow actions to the upgrade section prerequisites
Checklist
🚀 Deployment available! Here are the direct links to the updated files: