mergermarket/cdflow2-config-azure Docker 镜像 - 轩辕镜像

mergermarket/cdflow2-config-azure

• mergermarket/cdflow2-config-azure on DockerHub
• mergermarket/cdflow2-config-azure on GitHub

This container is for teams using cdflow2 to deploy services within Dealogic - i.e. Dealogic staff members and partners building services for Dealogic infrastructure. If this doesn't appy to you, consult the cdflow2 documentation to see if there is a config container that will work for your use-case (or how to build one).

Usage

cdflow.yaml:

yaml
version: 2
config:
  image: mergermarket/cdflow2-config-azure
  params:
    team: my-team-name
    env_subscription_id: azure-subscription-id
terraform:
  image: mergermarket/terraform-azure-ps

Parameters

team

This is the short name for your team - i.e. the name of your team's Jenkins folder as it appears in a Jenkins URL. Usually a team's deploy credentials will only have access to write release info, terraform state, etc to paths prefixed with the team's name, so this will need to be right for your pipeline to work.

[env]_subscription_id

This is used to link the environment name to a subscription id in Azure [env] should be replaced by the env name like (dev_subscription_id, prd_subscription_id).

What this config plugin provides

Release metadata

An additional team key is added to the release terraform map variable so that your terraform code can use it for tagging resources.

Storing the release

At the end of the release the config container is invoked to persist the release, including release metadata and terraform providers and modules.

Retrieving the release and deployment enironment

cdflow2 commands that require terraform to be configured (e.g. deploy, destroy, shell) use the config container to retrieve the release from Sotrage Account. The following is provided:

• As with all terraform config plugins, terraform map variables for each build with the build metadata, as well as a general release map with an additional team key (both persisted in the release).