bundle/deploy/lock: wire DMS into NewDeploymentLock via experimental.use_managed_state

When experimental.use_managed_state is set in databricks.yml, NewDeploymentLock
now creates a metadataServiceLock alongside the workspace-filesystem lock.
Acquire calls DMS CreateVersion after acquiring the file lock; Release calls
DMS CompleteVersion before releasing it.

Co-authored-by: Shreyas Goenka <shreyas.goenka@databricks.com>

Author: shreyas-goenka

bundle/config/experimental.go

@@ -42,6 +42,12 @@ type Experimental struct {
 	// Eventually this can be made the default once we have native CRUD in DABs
 	// at which point we can deprecate or remove this field all together.
 	SkipNamePrefixForSchema bool `json:"skip_name_prefix_for_schema,omitempty"`
+
+	// UseManagedState enables Deployment Metadata Service (DMS) integration.
+	// When set, each deployment registers a versioned record with the DMS API,
+	// providing server-side deployment history and concurrency control via
+	// the server-side version counter.
+	UseManagedState bool `json:"use_managed_state,omitempty"`
 }
 
 type Python struct {

bundle/deploy/lock/lock.go

@@ -57,6 +57,9 @@ func NewDeploymentLock(ctx context.Context, b *bundle.Bundle, goal Goal) *Deploy
 	if enabled {
 		l.wfs.client = b.WorkspaceClient(ctx)
 	}
+	if b.Config.Experimental != nil && b.Config.Experimental.UseManagedState {
+		l.dms = newMetadataServiceLock(b, goal)
+	}
 	return l
 }