You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar issues related to this rule have been reported several times; the most relevant ones seem to be #417, #713, #590 in all these cases they appear to be using a "bare" or "naked" Uri for which the recommended solution of uri() seems appropriate.
However, consider the following example ARM Template:
URIs Should Be Properly Constructed
[-] URIs Should Be Properly Constructed (11 ms)
Function 'concat' found within 'Some:SecretUri'
Function 'format' found within 'SecretUrl'
Function 'concat' found within 'Some:SecretUri' Line: 20, Column: 18
Function 'format' found within 'SecretUrl' Line: 20, Column: 18
Is there an alternate way that the Referenced Secret Syntax should be utilized that avoids this linter error? Even the alternative syntax @Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret) will throw because you're still going to need to use concat() or format() to accomplish this.
The real problem seems to be the detection of what is considered a URI, it appears to only considers properties that end in Uri or Url which is not a bad heuristic.
The text was updated successfully, but these errors were encountered:
Similar issues related to this rule have been reported several times; the most relevant ones seem to be #417, #713, #590 in all these cases they appear to be using a "bare" or "naked" Uri for which the recommended solution of
uri()
seems appropriate.However, consider the following example ARM Template:
This is using the Azure KeyVault Reference Syntax Documented here: https://learn.microsoft.com/en-us/azure/app-service/app-service-key-vault-references?tabs=azure-cli#reference-syntax. Both syntaxes will trigger the warning:
Is there an alternate way that the Referenced Secret Syntax should be utilized that avoids this linter error? Even the alternative syntax
@Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret)
will throw because you're still going to need to useconcat()
orformat()
to accomplish this.The real problem seems to be the detection of what is considered a URI, it appears to only considers properties that end in
Uri
orUrl
which is not a bad heuristic.The text was updated successfully, but these errors were encountered: