-
Notifications
You must be signed in to change notification settings - Fork 756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing type validation / inaccuracies #784
Comments
From a multi-resource deployment file:
|
The scope property on Microsoft.Authorization/roleAssignments is flagged as read-only but is available for PUT. |
Resource locks show as missing types: for a multi resource bicep file for a function app I get the following warnings when adding locks:
|
@sethwenzel - those are all "extension resources" and we'll have a simpler way for constructing them as we did with the scope property in JSON. Anything that has "providers" in the type (diags, roles, locks) will fall into that category. |
I've raised MicrosoftDocs/azure-docs#65815 to update our ARM template JSON samples. As @bmoore-msft mentioned, this should light up once we have https://github.com/Azure/bicep/blob/main/docs/spec/resource-scopes.md#resource-scope-property implemented. I've created #870 to track this independently. |
Warning BCP081: Resource type "Microsoft.KeyVault/vaults/secrets@2019-09-01" does not have types available. |
Warning BCP081: Resource type "Microsoft.Network/frontDoors/frontendEndpoints/customHttpsConfiguration@2020-07-01" does not have types available. |
Warning BCP081: Resource type "Microsoft.EventGrid/topics/providers/eventSubscriptions@2018-01-01" does not have types available. |
Resource type "Microsoft.RecoveryServices/vaults@2019-06-01" does not have types available. Ideally 'Microsoft.RecoveryServices/vaults/backupPolicies@2019-06-15' property Timezone should auto complete valid timezones Microsoft.Automation/automationAccounts@2015-10-31 is missing location as a required properties: location + Properties -> Sku -> name |
Resource type "Microsoft.DocumentDB/databaseAccounts/providers/diagnosticSettings@2017-05-01-preview" does not have types available. I don't know exactly which types you'd expect to provide |
Thanks for reporting @dgard1981 - this is a similar case to |
I would also suspect this is a similar case for other RBAC resource types. |
Whenever I'm trying to define an Azure Spring Cloud cluster (Microsoft.AppPlatform/Spring@2020-07-01), I'm not given an enum for sku.name or sku.tier
|
Originally reported with #791 -- Bicep version Describe the bug Furthermore, the properties.addressSpace is required in order for deployment to complete. To Reproduce
Types with issue (not exhaustive):
Additional context Expected
|
resource type 'Microsoft.KeyVault/vaults/secrets' gets autocompleted with a wrong API version. It gets completed to
|
Bicep version Describe the bug To Reproduce |
Bicep CLI version 0.2.46 (fa6e2c5) Element: Although reference (https://docs.microsoft.com/en-us/azure/templates/microsoft.web/certificates) describes |
Bicep version Describe the bug
To Reproduce
|
Warning BCP037: The property "publicNetworkAccess" is not allowed on objects of type "StorageAccountPropertiesCreateParametersOrStorageAccountProperties". Permissible properties include "allowSharedKeyAccess", "azureFilesIdentityBasedAuthentication", "customDomain", "isHnsEnabled", "isNfsV3Enabled", "largeFileSharesState", "routingPreference". According to https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts?pivots=deployment-language-bicep this is a valid property on a storage account. |
Double-check which API version you use. I had the same problem for different resource but then I've found I'm using old API version. |
It's not included in the ARM definition but works when I deploy my template with these two properties. |
/cluster-stamp.bicep(379,5) : Warning BCP037: The property "eTag" is not allowed on objects of type "SavedSearchProperties". Permissible properties include "functionAlias", "functionParameters", "tags". |
In The help text in the VS Code intelisense even states There are very specific values that are allowed here as listed in the error message: |
Bicep Template:
Bicep Warning:
If I try and use something like 'Web', the deployment will fail with error:
|
Azure SQL Server serverless database allows Min vCores to be 0.5, but Bicep says 'The property "minCapacity" expected a value of type "int | null" but the provided value is of type "'0.5'".'
|
Azure Data Factory Linked Service:
Warning:
Note that there is no
|
|
|
API Version: 2022-07-01 Warning BCP037: The property "enableCustomCATrust" is not allowed on objects of type "ManagedClusterAgentPoolProfile". Permissible properties include "availabilityZones", "creationData", "enableFIPS", "gpuInstanceProfile", "hostGroupID", "kubeletConfig", "kubeletDiskType", "linuxOSConfig", "maxCount", "maxPods", "minCount", "nodeLabels", "nodePublicIPPrefixID", "nodeTaints", "orchestratorVersion", "osDiskSizeGB", "osDiskType", "osSKU", "podSubnetID", "powerState", "proximityPlacementGroupID", "scaleDownMode", "scaleSetEvictionPolicy", "scaleSetPriority", "spotMaxPrice", "type", "upgradeSettings", "workloadRuntime" |
When attempting to get Bicep file for existing APIM resource. (Get
The issue seems to be with the decompiler and not the bicep expected types for the resource. sampling: {
percentage: '100'
samplingType: 'fixed'
} sampling: {
percentage: 100
samplingType: 'fixed'
} |
var managedResourceGroupId = '${subscription().id}/resourceGroups/${resourceGroupName}-${managedResourceGroupName}-${replace(publishers[publisher].version,'.','-')}'
resource hordeStorage 'Microsoft.Solutions/applications@2017-09-01' = {
location: location
kind: 'MarketPlace'
name: appName
plan: publishers[publisher]
properties: {
managedResourceGroupId: managedResourceGroupId
parameters: {...}
jitAccessPolicy: null
}
} |
Warning BCP037: The property "certificateSource" is not allowed on objects of type "HostnameConfiguration". Permissible properties include "certificatePassword", "encodedCertificate", "identityClientId", "keyVaultId". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
|
Every time I play my bicep on Cosmos DB it indicates removing those properties which aren't available in schema :
I'm not sure if it should be configurable but in this case it should at least be ignored. |
On the documentation page:
Can anyone tell me why the id field is mandatory while it references to the resource itself? |
Warning BCP081: Resource type "Microsoft.MachineLearning/workspaces@2022-10-01" does not have types available |
parameterValueType missing on 'Microsoft.Web/connections@2016-06-01' |
I am given warning that
warning message
|
Got this warning on Service Bus namespaces Resource type "Microsoft.ServiceBus/namespaces@2022-10-01-preview" does not have types available. bicep(BCP081) resource serviceBusResource 'Microsoft.ServiceBus/namespaces@2022-10-01-preview' = { |
For 'Microsoft.DataFactory/factories/triggers@2018-06-01': Warning BCP037: The property "pipelines" is not allowed on objects of type "ScheduleTrigger' For 'Microsoft.DataFactory/factories/pipelines@2018-06-01': Warning BCP037: The property "policy" is not allowed on objects of type "Lookup" |
.\main.bicep(101,17) : Warning BCP036: The property "maxPrice" expected a value of type "int | null" but the provided value is of type "'0.0x'". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues] |
For 'Microsoft.Web/sites/basicPublishingCredentialsPolicies@2022-03-01' |
Not sure if this is the place for documentation issues, but https://learn.microsoft.com/en-us/azure/templates/microsoft.servicefabric/managedclusters/nodetypes?pivots=deployment-language-bicep doesn't provide anything more appropriate. In any case: for name: limited to 9 chars, but this isn't documented. |
We will be moving all azure type inaccuracy issues to this repo: https://github.com/Azure/bicep-types-az You can submit/document an issue with this form here: https://aka.ms/bicep-type-issues |
Please submit all type inaccuracy issues to the Bicep Types Repo here: https://aka.ms/bicep-type-issues
The text was updated successfully, but these errors were encountered: