Skip to content

Rename-DbaDatabase - Build expected file paths without validating drives of the test client - #10606

Open
andreasjordan wants to merge 1 commit into
developmentfrom
fix-renamedbadatabase-remote-drive
Open

Rename-DbaDatabase - Build expected file paths without validating drives of the test client#10606
andreasjordan wants to merge 1 commit into
developmentfrom
fix-renamedbadatabase-remote-drive

Conversation

@andreasjordan

Copy link
Copy Markdown
Collaborator

Summary

The physical-name template test builds its expected paths with Join-Path from the file paths of the instance. Windows PowerShell validates the drive qualifier of Join-Path against the drives of the machine running the test, so against a remote instance whose files live on a drive the test client does not have - such as a failover cluster instance keeping its databases on a clustered disk - the test fails with "Cannot find drive. A drive with the name 'S' does not exist" although the command works.

Changes (tests only)

The four expected paths are now built with [System.IO.Path]::Combine, which composes strings without touching the provider - and is also what Rename-DbaDatabase itself builds the new path with, so the expectation mirrors the command exactly.

Verified against a clustered instance with databases on a clustered drive (the previously failing shape) and against a regular instance, both warning-free with all tests passing.

created by Claude and reviewed by Andreas Jordan

🤖 Generated with Claude Code

…ves of the test client

(do Rename-DbaDatabase)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant