Deployment Pipeline enhancements - change from 'pull' to 'push' methodology

[Thomas_Pouliot]

Right now:

• In deployment pipeline (new version) to deploy from dev to test we have to click test then select the item from dev we want deployed and then deploy. (essentially pulling up from the lower stage versus pushing to the next)
• If we want to set rules we have to deploy first THEN set the rule which is counterintuitive and a time sink/waste of resources to then deploy again or manually change the parameters.
• The icon for deployment is a rocketship not a UFO with a tractorbeam so I think push is the intention not a pull.
  • This imagery should convey what I mean when I say push (rocket propulsion) versus pull (UFO tractor beam)

Suggested change:

• Change from a pull deployment to a push deployment
  • Change Deploy From to Deploy To.
  • To deploy from dev to test, user should click on DEV and select report to deploy to test
  • Before deploy user should be able to set any parameter and data source change rules.
    • Remove rules from highest prod level, add rules to lowest dev level
  • Then user can click deploy to have it moved/pushed/deployed up to test.
• All gateway settings and parameters should be settable through deployment pipeline and pipeline should tell if there is no gateway
• Add checkbox option to deployment - Refresh on deployment
  • This option should be grayed out or fail without using resources if a gateway is not setup.
  • When checked, after successful deployment, attempt to refresh the report without user having to go into the workspace to refresh it.
• Add global parameter rules as noted in separate idea Global Deployment Pipeline Rules - Microsoft Fabric Community