It is unclear how to use --enable-managed-virtual-network --enable-managed-vnet
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 64
Description
**Related command**
it is unclear how to use --enable-managed-virtual-network --enable-managed-vnet
The flag indicates whether enable managed virtual network.
accepted values: false, true
**Is your feature request related to a problem? Please describe.**
I try this:
` az synapse workspace create --name $synapseWorkspaceName --resource-group $resourceGroupName --storage-account $storageAccountName --managed-rg-name $synapseWorkspaceNameManaged \
--file-system $fileShareName \
--location $location \
--sql-admin-login-user 'sqladminuser' \
--sql-admin-login-password '' \
--repository-type AzureDevOpsGit --account-name $myGitProjectAccountName --project-name $myGitProjectName --tenant-id $tenantId --repository-name $myGitRepositoryName --collaboration-branch $myGitCollaborationBranch
--enable-managed-virtual-network true
--enable-managed-vnet true`
**Describe the solution you'd like**
Must be understandable. With an example is already helpful.
**Describe alternatives you've considered**
Manually turning on. Azure CLI is not of full use.
**Additional context**
Nope.
Contributor guide
Research direction
Start with the `az synapse workspace create` command and its `--enable-managed-virtual-network` and `--enable-managed-vnet` options. Reproduce the reported command with a minimal example, then clarify the accepted boolean values and document an understandable working example; done means the CLI help or command documentation explains how to use the options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cli, cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100