Azure Overview
For the following examples we will assume that the Furnace Instance has been called
furninst and that the stack being deployed is called furnstak and we are deploying the dev environment.- Resource Group (
{stack name}rgie.furninstrg)- Used to group all the Furnace Instance resources
- Storage
{stack name}artifactsiefurninstartifactsused to store the module/function code{stack name}bootstrapiefurninstbootstrapused to store the deploy code
- App Service (
{resource group name}-deployiefurninstrg-deploy)- Contains the functions for deploy
deploy-triggerAccepts webhook request from Github and puts a message into the deploy EventHub queuedeploy-execTriggered by events on the deploy EventHub queue and launches the deploy container.
- App Insights
- Event Hubs Namespace (
{resource group name}-deployHubNSiefurninstrg-deployHubNS)- Contains the Event Hub Instance
{resource group name}-deployhubto receive messages from thedeploy-triggerfunction
- Key Vault (
{resource group name}-vaultiefurninstrg-vault)- Used for storing secrets
- User Assigned Identity (
FurnaceDeployUserIdentity)
- Resource Group (
{stack name}-RG-{environment}iefurnstak-RG-dev)- Contains the stack resources
- Event Hubs Namespace ({stack name}-hubns-{environment} ie
furnstak-hubns-dev)- Contains the Event Hub Instances for the queues between functions
- Source Event Hub will be named
{stack name}-{source name}-{environment}ie for a source name ofsource1it would befurnstak-source1-dev - Function events will have output Event Hubs created as
{stack name}-{function name}-out-{environment}so if our function was calledfunction1it would befurnstak-function1-out-dev
- Container Group
- Contains the container for deploying the stack
- Sink resources as described in the stack
Logs for deployment can be found in the Container Group resource in the stack Resource Group.
For some reason you may get a 500 error on the deploy function trigger, if this happens try restarting the deploy function app.
Last modified 4yr ago