Skip to content
This repository was archived by the owner on Feb 15, 2022. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions gitops/azure-devops/ImageTagRelease.md
Original file line number Diff line number Diff line change
Expand Up @@ -189,6 +189,8 @@ Now that we have created a release pipeline with environment specific configurat
<b>FAB_ENVS: 'DEV,QA,STAGING WEST,STAGING EAST,STAGING CENTRAL,PROD WEST,PROD EAST,PROD CENTRAL'</b>
</pre>

Note: If you followed the preceding [manifest generation pipeline](ManifestGeneration.md) tutorial, remember to remove the FAB_ENVS variable from the Azure pipeline you created, as its value will replace the value specified here.

The **bolded** key and values represent specific environments we want Fabrikate to generate yaml for. Notice that the comma delimited values contain a subset of the environment names we configured as Azure DevOps release pipeline stages and HLD repo configuration.

Once we add the appropriate `FAB_ENVS` values the manifest generation pipeline will produce resource manifests for each directory
Expand Down