https://github.com/sjkp/dns-proxy

https://github.com/sjkp/dns-proxy

Last synced: 8 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/sjkp/dns-proxy
• Owner: sjkp
• Created: 2022-06-23T19:45:38.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-06-23T23:08:02.000Z (over 2 years ago)
• Last Synced: 2024-04-15T02:56:02.901Z (7 months ago)
• Language: Bicep
• Size: 7.81 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Azure Container Apps - Infrastructure Template 

Use this template to create an Azure Container App repository that configures an Azure environment ready for use for hosting docker containers. It uses the subscription deploy scope, so you need a service principal with access to the subscription where you want to deploy the resource group. 

Besides Azure Container Apps, it deploys a storage account and an Azure Key Vault, and log analytics workspace. 

Things you want to modify

| Location | Usage |

| - | - |

|.github/workflows/deploy.yaml| For the github action to work you must set the following Secrets: `AZURE_CREDENTIALS`, `AZURE_SUBSCRIPTION`, and `AZURE_APP_NAME` you can also change the region, if you don't want to use north europe for logging. *If you need an Azure Container App that uses an Azure file share mount you can use the template `main-with-storage.bicep` instead of just main in `deploy.yaml`*

| infrastructure/params.json | You can change the `location` of the resource group (all resource are deployed to same location) and the `appName` in here, `appName` is used to generate the name of all the resources and the resource group. You can also change which `containerImage` that you want deployed, it defaults to nginx |

## Manual Deployment

```

az deployment sub create --location northeurope --template-file infrastructure/main.bicep --parameters infrastructure/params.json

```

## Github Action Deployment

When generating your credentials (in this example we store in a secret named AZURE_CREDENTIALS) you will need to specify a scope at the subscription level.

```

az ad sp create-for-rbac --name "{sp-name}" --sdk-auth --role contributor --scopes /subscriptions/{subscription-id}

```

Note: the `sp-name` must be a subdomain of your tenant name, e.g. `ghaction..onmicrosoft.com`