Skip to content

Fix /OutputPath conflict in DeployReport, DriftReport, and Script actions in SqlAzureDacpacDeploymentV1#21982

Open
v-dko wants to merge 3 commits intomasterfrom
users/v-dko1/sqldacpacdeploymentdriftissuefix
Open

Fix /OutputPath conflict in DeployReport, DriftReport, and Script actions in SqlAzureDacpacDeploymentV1#21982
v-dko wants to merge 3 commits intomasterfrom
users/v-dko1/sqldacpacdeploymentdriftissuefix

Conversation

@v-dko
Copy link
Copy Markdown
Contributor

@v-dko v-dko commented Apr 9, 2026

Context

When users pass /OutputPath in additional arguments, the task overrides it with a hardcoded default path, causing the user-specified output location to be ignored.
Git Issue: #20659
Bug: https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2269716/


Task Name

SqlAzureDacpacDeploymentV1


Description

Adds a SqlAzureDacpac.EnableUserOutputPath feature flag that, when enabled, detects user-provided /OutputPath in additional arguments and skips injecting the default output path, fixing the conflict in DeployReport, DriftReport, and Script actions


Risk Assessment (Low / Medium / High)

low


Change Behind Feature Flag (Yes / No)

Yes- SqlAzureDacpac.EnableUserOutputPath(Dynamic Feature flag)


Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

  • User guides, API specs, system diagrams, or runbooks are updated.

Unit Tests Added or Updated (Yes / No)

NO

Additional Testing Performed

Manually tested working as expected

Logging Added/Updated (Yes/No)

no


Telemetry Added/Updated (Yes/No)

  • Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
  • Events are tagged with proper metadata for filtering and analysis.
  • Telemetry is validated in staging or test environments.

Rollback Scenario and Process (Yes/No)

Disable Featureflag SqlAzureDacpac.EnableUserOutputPath.


Dependency Impact Assessed and Regression Tested (Yes/No)

  • All impacted internal modules, APIs, services, and third-party libraries are analyzed.
  • Results are reviewed and confirmed to not break existing functionality.

Checklist

  • Related issue linked (if applicable)
  • Task version was bumped — see versioning guide
  • Verified the task behaves as expected

@v-dko v-dko requested review from a team and manolerazvan as code owners April 9, 2026 10:01
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
Successfully started running 3 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant