0

We have two static apps, one for production and one for non production (test). They just show a site down page for when our main site on AEM is down (using traffic manager to switch).

The source is held in an Azure devops git repo.

This is how it is built in non prod:

trigger:
  - main

pool:
  vmImage: ubuntu-latest

steps:
  - checkout: self
    submodules: true
  - task: AzureStaticWebApp@0
    inputs:
      app_location: '/'
      api_location: ''
      output_location: ''
      azure_static_web_apps_api_token: $(deployment_token)

Now we want to make it build a prod version of the static web app, if we push to another branch (e.g. "prod"). Any idea how we might do this? Not sure how we would differentiate between the prod static web app deployment token and the non prod one either?

John Little
  • 10,707
  • 19
  • 86
  • 158

1 Answers1

0

Please take a look on this example. Here you have three main steps:

  • in stage Build - a package is being prepared
  • in stage Dev - package is being deployed to Dev env
  • in stage Prod packages is being deployed to Prod env

It is implementation of approach build once deploy many, which is good because it means that on each env you use the same package, so you trully test the package which is going to be deployed to production.

In terms of token, you can put this is two seprate variables group. One name dev, and the other prod. Both should have the same variable deployment_token and then

- stage: Prod
  dependsOn: Dev
  variables:
  - group: Prod


- stage: Dev
  dependsOn: Build
  variables:
  - group: Dev
Krzysztof Madej
  • 32,704
  • 10
  • 78
  • 107