A bundle feature in Beta that logs who deployed, which Git commit and what resources changed. It works on a best-effort basis and requires the direct deployment engine.
Read more: Databricks docs
In the Ultra Transcenders books
Each book explains Deployment history in context, with comparison tables and the common traps.
Terms in this definition
- Git
A distributed version control system. Anything kept in Git, prompts included, gains a history of authors, timestamps, diffs and tags, and changes can be reverted.
- Direct deployment engine
Deploys bundles with no reliance on the Terraform provider, the original foundation for bundles.
Related terms
- Deployment environment
A named target for deployments. Azure Pipelines environments group VMs or Kubernetes namespaces, track deployment history and carry checks and approvals; GitHub environments carry secrets and protection rules. Unrelated to Azure Machine Learning environments.
- Export template
Produces a template reflecting resources as they currently are, whereas deployment history keeps the template that was actually deployed. It used to be called Automation script.
- @secure() decorator
Bicep decorator marking a parameter or output of type string or object as sensitive, so its value is kept out of Resource Manager logs and deployment history.