Skip to content

Support volume_path in direct deploy engine#4611

Open
varundeepsaini wants to merge 1 commit intodatabricks:mainfrom
varundeepsaini:ft/volume-path-support
Open

Support volume_path in direct deploy engine#4611
varundeepsaini wants to merge 1 commit intodatabricks:mainfrom
varundeepsaini:ft/volume-path-support

Conversation

@varundeepsaini
Copy link
Contributor

@varundeepsaini varundeepsaini commented Feb 27, 2026

Closes #4233

Summary

  • Add computed volume_path field to VolumeRemote in the direct engine, matching the Terraform provider's behavior (/Volumes/{catalog}/{schema}/{name})
  • This enables ${resources.volumes.foo.volume_path} interpolation without requiring the workaround of manually constructing the path from individual name components

Test plan

  • Unit tests for makeVolumeRemote (full name and fallback paths)
  • Unit test for RemapState excluding volume_path from diff comparison
  • Acceptance test: schema classifies volume_path as REMOTE field
  • Acceptance test: plan shows correct dependency graph when referencing volume_path
  • Acceptance test: full deploy/destroy lifecycle with cross-volume volume_path reference
  • Acceptance test: no drift detected after deploy (0 to change)

Tests written by Claude

CloudEnvs.azure = false

[EnvMatrix]
DATABRICKS_BUNDLE_ENGINE = ["direct"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we run this on direct only?

type VolumeRemote struct {
catalog.VolumeInfo

VolumePath string `json:"volume_path,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we add this only on remote struct? This is something we can calculate from the local as well, right?

I wonder if we should just to config and evaluate early.

Signed-off-by: Varun Deep Saini <varun.23bcs10048@ms.sst.scaler.com>
@github-actions
Copy link

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 4611
  • Commit SHA: 4f79a2ba6884734e7ef8e7e49e33df2033f3011c

Checks will be approved automatically on success.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

volumes: volume_path field is not available

2 participants