Need help: Dynamically updating parameter values during Fabric CI/CD deployment

$workspaceId = "your-workspace-id"
$pipelineId = "your-pipeline-id"
$bearerToken = "your-token"

$body = @{
    definition = @{
        parts = @(
            @{
                path = "pipeline-content.json"
                payload = @{
                    activities = @(...)
                    parameters = @{
                        connectionId = @{
                            type = "String"
                            defaultValue = "prod-connection-id"
                        }
                        databaseName = @{
                            type = "String"
                            defaultValue = "ProductionDB"
                        }
                    }
                }
            }
        )
    }
} | ConvertTo-Json -Depth 10

Invoke-RestMethod -Uri "https://api.fabric.microsoft.com/v1/workspaces/$workspaceId/items/$pipelineId/updateDefinition" -Method Post -Headers @{Authorization = "Bearer $bearerToken"} -Body $body -ContentType "application/json"
```

**Option 2: Environment-Specific Definition Files**

Store separate pipeline definition JSON files for each environment in your repo:
```
/pipelines
  /dev
    pipeline-config.json
  /test
    pipeline-config.json
  /prod
    pipeline-config.json

During deployment, reference the correct file based on your target environment variable.

Option 3: Notebook Parameters Workaround

For Notebooks specifically, use Azure DevOps variable groups and pass parameters at runtime:

# In your notebook
dbutils.widgets.text("environment", "dev")
dbutils.widgets.text("connectionString", "default")

env = dbutils.widgets.get("environment")
connString = dbutils.widgets.get("connectionString")

Then schedule or trigger the notebook with environment-specific parameter values through the Fabric API.

Option 4: Post-Deployment Script

Create a PowerShell script in your pipeline that reads environment variables and updates Fabric items:

- task: PowerShell@2  inputs:
    targetType: 'inline'
    script: |
      $env = "$(Environment)"      $configFile = Get-Content "./config/$env.json" | ConvertFrom-Json
      
      # Update pipeline parameters via REST API
      # Call Update Definition API with environment-specific values

The GitHub sample you referenced focuses on deployment but doesn't handle parameter substitution. You need to add a custom step after the deployment task.

If you need to do a lot of parameter replacement I strongly recommennd looking to use the fabric-cicd Pythin library as a layer of abstraction instead of working with the API's directly.

https://microsoft.github.io/fabric-cicd/0.1.30/ 

Hi CloudVasu,

We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

KevinChant & MJParikh ,Thanks for your prompt response

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support

Hi CloudVasu,

We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support