Skip to content

fix(azure): bastion subnet name check and public IP in-use message - #1546

Merged
NitinKumar004 merged 2 commits into
developmentfrom
fix/azure-bastion-pip-msg
Oct 11, 2026
Merged

NitinKumar004 merged 2 commits into
developmentfrom
fix/azure-bastion-pip-msg

Conversation

@NitinKumar004

@NitinKumar004 NitinKumar004 commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator
  • A Bastion host whose ipConfiguration subnet is not named AzureBastionSubnet now fails with 400 InvalidParameter (AZNET-22)
  • Deleting a public IP that is still allocated returns 400 PublicIPAddressCannotBeDeleted naming the public IP's ARM id instead of the internal allocation id (AZNET-13)

Tested: new tests in server/azure/bastion and server/azure/vnet; go test on the touched packages; lint clean.

@NitinKumar004
NitinKumar004 marked this pull request as ready for review October 11, 2026 19:50
@NitinKumar004
NitinKumar004 merged commit 48e274d into development Oct 11, 2026
23 checks passed
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