Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support client code and environment templating in ARM parameter file names #75

Open
gnadaban opened this issue Sep 28, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@gnadaban
Copy link

Is your feature request related to a problem? Please describe.
It's tedious to have to hardcode client and environment information in the puff map file.

Describe the solution you'd like
Deploy manager should support templating in puff file fields, so that this:

puff_map:
  frames:
    coredata:
      applications:
        actiongroup:
          arm_parameters_files:
            ftr:
              egms_fdx_devd:
                coredata-team-monitor-integrations: actiongroup.coredata-team-monitor-integrations.fdx.egms_fdx_devd.json

Could be templated like this:

puff_map:
  frames:
    coredata:
      applications:
        actiongroup:
          arm_parameters_files:
            ftr:
              egms_fdx_devd:
                coredata-team-monitor-integrations: actiongroup.coredata-team-monitor-integrations.${CLIENT_CODE}.${SUBSCRIPTION}.json

This would:

  1. Simplify maintenance of puff files because we would not have to hardcode the same redundant information all over that is already available within the context of the deployment
  2. Allow us to have a single, default Puff Map, with the client-specific ones becoming optional in case we want to deploy only a subset of resources
  3. Allow us to rely on the common shared Puff map to do feature branch deployments with pseudo-random client codes per branch
@blueskyjunkie blueskyjunkie added the enhancement New feature or request label Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants