Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update build-data-pipeline.md to remove unavailable extension #14240

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

akoppanur
Copy link
Contributor

DevOps for Azure Databricks extension is no longer available. Here is the pipeline yml file that refers to the unavailable extension:
https://github.com/MicrosoftDocs/azure-devops-docs-samples/blob/main/azure-data-pipeline/data_pipeline_ci_cd.yml

Customers have reported this issue and requested alternate methods. See here: microsoft/azdo-databricks#43 This documentation needs to be updated to provide our own custom script for deployment to Azure Databricks and ADF or documentation to be removed.

There is an alternate third-party extension:
https://marketplace.visualstudio.com/items?itemName=DataThirstLtd.databricksDeployScriptsTasks

 DevOps for Azure Databricks extension is no longer available. Here is the pipeline yml file that refers to the unavailable extension:
   https://github.com/MicrosoftDocs/azure-devops-docs-samples/blob/main/azure-data-pipeline/data_pipeline_ci_cd.yml
 
Customers have reported this issue and requested alternate methods. See here: microsoft/azdo-databricks#43
This documentation needs to be updated to provide our own custom script for deployment to Azure Databricks and ADF or documentation to be removed.

There is an alternate third-party extension:
  https://marketplace.visualstudio.com/items?itemName=DataThirstLtd.databricksDeployScriptsTasks
Copy link
Contributor

@akoppanur : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ttorble
Copy link
Contributor

ttorble commented Feb 12, 2025

@juliakm

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

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

Successfully merging this pull request may close these issues.

3 participants