Forum Discussion

JacobJoo's avatar
JacobJoo
New Member
7 months ago
Solved

Issue with Deployment movement from QA to Prod

Hello Community, We’re currently facing challenges while moving artifacts from lower environments to higher environments (QA to Prod). We tried using deployment pipelines, but it became quite messy ...
data engineering
data pipeline
  • deborshi_nag's avatar
    deborshi_nag
    7 months ago

    Hello JacobJoo 

     

    The challenges you’re encountering with deployment on Fabric are quite typical. While your current approach is effective, it does involve additional manual effort.

     

    I suggest implementing GIT integration for your workspaces, with only the Dev environment set to writable and QA and Prod configured as read-only from their respective GIT branches.

     

    Additionally, be sure to parameterise all environment-specific variables and references, such as Lakehouse names, Warehouses, and SQL endpoints.

     

    For promoting to higher environments, it is preferable to use Pull Requests rather than deployment pipelines.

     

deborshi_nag's avatar
deborshi_nag
Super User
7 months ago

Hello JacobJoo 

 

The challenges you’re encountering with deployment on Fabric are quite typical. While your current approach is effective, it does involve additional manual effort.

 

I suggest implementing GIT integration for your workspaces, with only the Dev environment set to writable and QA and Prod configured as read-only from their respective GIT branches.

 

Additionally, be sure to parameterise all environment-specific variables and references, such as Lakehouse names, Warehouses, and SQL endpoints.

 

For promoting to higher environments, it is preferable to use Pull Requests rather than deployment pipelines.