iac | Infrastructure as Code for various projects | Azure library

Well the "rewrite ... redirect" is executed by the client the "proxy_pass ..." from nginx servers.

I see 2 options:

• Add resolver to the config
• use 127.0.0.1 for localhost so that no resolving is necessary.

You can see the problem with resolving in this log line.

Tested in my environment working fine for me you need to change image name for azure-vote-front from image: microsoft/azure-vote-front:v1 to image: mcr.microsoft.com/azuredocs/azure-vote-front:v1.

Would using create ifnotexists work for you?

I found the solution by manually searching in azure-quickstart-templates. At the bottom of the page: Microsoft.Cdn profiles/afdEndpoints/routes 2020-09-01, I found the template Front Door Standard/Premium. After analyzing the main.bicep file here, the compression settings must be set as follows:

There's no theoretical security problems to storing public keys in a repository. The conceptual idea of a public key is that it is known to everyone: the whole world knows it.

Now, as a practical matter, because a public key usually uniquely identifies a user, if someone gets ahold of that key, they may be able to correlate it with other locations where that user uses that key (e.g., GitHub, where all SSH keys are public) and decide that the user in question is an interesting target for phishing or other types of compromise based on correlating that user's usage.

This is one of those cases where the theoretical and practical security differs. Having said that, most people don't consider exposure of public keys a threat they have to deal with, and so checking them into a repository should be fine.

The problem was at this place:

I am trying to write the Terraform to create an Azure "service account" and am getting quite confused by the distinction between what Azure AD calls "Applications" and "Service Principals".

Applications can be seen from Azure AD App registrations blade Where as Service Principals are other wise know as Enterprise Applications. The difference is well documented in this Microsoft Documentation.

This runs, but later authenticating with the generated credentials gives an authentication error. Specifically, Terraforms says:

If you are accessing as application please make sure service principal is properly created in the tenant.

This is because you have no associated service principal to that azure ad application which you have created from Terraform. The association is needed to access the application or authenticating to the azure environment with contributor role. When a App registration is created from portal it by default creates an association of AD app and Service principal , which by default results in creating a service principal for that app registration. It also applies the same concept when we use az ad sp create-for-rbac.

Effectively, I'm trying to mimic the following Azure CLI call:

I have tested in my environment

As per the azurerm_api_management_api | Resources | hashicorp/azurerm | Terraform Registry document, there is no option to set a tag to an API in Azure API Management using Terraform.

We can create an API tag for Azure API Management using terraform using below code :

So if wanted to use a variable group need to define the group to be read in: