variable-library-cli

Create a Variable Library by POSTing to /v1/workspaces/{ws}/items with type VariableLibrary and base64-encoded definition parts: variables.json, settings.json, and valueSets/<name>.json files. Omit the format field entirely, as Variable Library definitions reject it.

Add a libraryVariables block under pipeline properties with libraryName, libraryId, variableName, and type, then reference it with the expression @pipeline().libraryVariables.<name>. The expression must be an object with type Expression, not a bare string.

The active value set is workspace item state, not definition, so it is never serialized to Git. Verify it with GET /variableLibraries/{id}, which returns properties.activeValueSetName; the generic /items/{id} endpoint omits properties.

Each variableOverrides value must use the variable's native JSON type, such as a real boolean or number, not a string. The REST documentation lists the field as String, but the live API rejects stringified booleans and numbers.

Use notebookutils.variableLibrary.getLibrary("LibraryName") and access variables as properties, or call notebookutils.variableLibrary.get with the $(LibraryName/VariableName) path. Coerce Boolean values defensively with str(value).lower() == "true" since they may arrive as strings.

Use the fabric-cicd Python package for full CI/CD deployment automation, as it supports VariableLibrary as an item type. Use direct REST calls for targeted tasks like creating a library or switching the active value set in one workspace.