Context:

env() doesn't have it (as you've noticed) - we removed that endpoint from the ttk check for the reasons discussed here 😉 - we should probably remove it from the linter too…

From: John Downs <John.Downs@microsoft.com>
Sent: Tuesday, February 22, 2022 11:57 AM
To: Trevor Cooper-Chadwick <[Trevor.Cooper-Chadwick@microsoft.com](mailto:Trevor

Description

Verify the optional vs required description for all parameters is correct, i.e. parameter description should start with "Optional" if a default value is provided, "Required" otherwise.

Can be performed per resource provider.

Could be automated leveraging regex.
If so, could also be added to the static validation, as a separate issue.

Rule request

Suggested rule change

Similar to Azure.Redis.MinTLS, we should include Microsoft.Cache/redisEnterprise type as well to check the minumumTlsVersion property: https://docs.microsoft.com/en-us/azure/templates/microsoft.cache/redisenterprise?tabs=bicep#clusterproperties.

I guess we need to decide if this should be a new rule or simply add this type to the existing rule

Creation of a sample to include importing containers into an ACR as part of the deployment.

This would require

• New managed identity
• RBAC for the identity to be able to run ACR imports
• Creation of an AZ CLI script to do the container image importing into ACR
• Creation of a bicep resource DeploymentScript to run the AZ CLI script conditionally during deployment

Was wondering if anyone had looked at converting the cloud guardrails for cloud profile 3 into the custom policies in this repo.

I know some of the documentation for controls has been uploaded here
https://github.com/canada-ca/cloud-guardrails-azure

and here

https://github.com/canada-ca/cloud-guardrails