Calling Azure REST API
This blog Calling Azure REST API via curl is pretty good. Just two more things.
This blog Calling Azure REST API via curl is pretty good. Just two more things.
For people who encounter UnicodeEncodeError
when using Windows Azure Pipeline agent, the issue might be here.
As per above link, or this email, the solutions could be:
PYTHONIOENCODING=UTF-8
.PYTHONUTF8=1
, or by passing the command-line option -X utf8
.The example given by this post is for Azure Pipeline with the latest Ubuntu agent, for AzCli from local machine, removing the --auth-mode login
part should work.
As it's a Linux pipeline agent, the pipeline task AzureFileCopy can not be used, it's written in Powershell, we should use the AzureCLI task instead.
Suppose we're running following job/task in a Azure Databricks workspace:
jobId: "1111"
jobRunId: "2222"
taskRunId: "3333"
jobName: "ths job name"
taskName: "first-task"
databricksWorkspaceUrl: https://adb-4444444444.123.azuredatabricks.net/
Run below command in a Databricks job (task precisely):
Azure pipeline has two kinds of conditions:
condition
${{if elseif else}}
In both syntax, we have use parameters and variables, but there's a big difference between them which makes DevOps frustrated.
This post will talk about some Azure pipeline predefined variables' values in a multiple repositories checkout situation. The official doc is here.
Most of Databricks management can be done from the GUI or CLI, but for Azure Service Principal, we can only manage it by the SCIM API. There's an open PR for adding support of SCIM API in Databricks CLI, but the lastest update is back to the beginning of 2021.
This post is to add some tips that not covered by the official API docs.