[BUG] no convenience API to set PublicNetworkAccess in Vault #39192
Labels
ARM
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Mgmt
This issue is related to a management-plane library.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
azure sdk for java does not offer diable PublicNetworkAccess for keyvaults
Exception or Stack Trace
import com.azure.identity.DefaultAzureCredential;import com.azure.resourcemanager.AzureResourceManager;import com.azure.resourcemanager.keyvault.models.Vault;import com.azure.resourcemanager.keyvault.models.VaultCreateOrUpdateParameters;import com.azure.resourcemanager.keyvault.models.VaultProperties;import com.azure.resourcemanager.resources.fluentcore.arm.Region;import com.azure.resourcemanager.resources.fluentcore.utils.ResourceManagerUtils;
public class CreateKeyVaultExample {
public static void main(String[] args) {
String subscriptionId = "";
String resourceGroupName = "";
String keyVaultName = "";
}
To Reproduce
When coding with to the SDK properties there is no .withPublicNetworkAccess to set to False
It creates it with PublicNetworkAccess enabled
Code Snippet
See above
Expected behavior
To be able to disable publicNetwokAccess
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
If you suspect a dependency version mismatch (e.g. you see
NoClassDefFoundError
,NoSuchMethodError
or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:mvn dependency:tree -Dverbose
)Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: