Skip to content

feat: add direct virtualization support - #49

Merged
Martin Heberling (Bickor) merged 3 commits into
Azure:mainfrom
Bickor:feat/direct-virtualization
Sep 17, 2026
Merged

Martin Heberling (Bickor) merged 3 commits into
Azure:mainfrom
Bickor:feat/direct-virtualization

Conversation

@Bickor

@Bickor Martin Heberling (Bickor) commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add the DirectVirtualization value for the SupportedVirtualizationTypes SKU capability
  • expose SKU.IsDirectVirtualizationSupported() in both the legacy and v2 packages
  • use the existing HasCapabilityWithSeparator capability handling for both nested and direct virtualization
  • test that the valid NestedVirtualization and DirectVirtualization API values do not match each other

The Compute API reports these virtualization types as mutually exclusive values, not as a combined collection.

Testing

  • go test -race ./... (root module)
  • go vet ./... (root module)
  • go test -race ./... (v2 module)
  • go vet ./... (v2 module)

golangci-lint could not load the repository's legacy configuration with the locally installed golangci-lint v2.4.0.

The repository coverage workflow currently fails during dependency setup before running tests: it pins Go 1.25 but installs golang.org/x/tools@latest, which now requires Go 1.26.

Comment thread v2/sku_test.go Outdated
Comment thread v2/sku.go
@Bickor
Martin Heberling (Bickor) merged commit 708ff8c into Azure:main Sep 17, 2026
2 checks passed
@Bickor
Martin Heberling (Bickor) deleted the feat/direct-virtualization branch September 17, 2026 22:01
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.

2 participants