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

Feat: Allow param filename configuration per target with the CFn provider + bugfixes #565

Merged
merged 5 commits into from
Dec 14, 2022

Conversation

sbkok
Copy link
Collaborator

@sbkok sbkok commented Dec 12, 2022

Why?

Allowing a specific parameter file to be used. This is especially useful if you
would like to reuse a template. Often these templates are committed or generated
with another generator than generate_params.py.

What?

  • Added params_filename to the CloudFormation provider schema.
  • Updated the CloudFormation provider to support setting the params_filename.
  • Documented the param_filename property in the CloudFormation provider docs.

Additionally, I refactored the adf_codepipeline.py file. As this file was not following
the line length requirements. When the line length was updated before, the resulting
code was hardly readable.

After this change, I realized a number of the properties were not configured correctly.
It would use the default_provider configuration first, and when that was not set
it would fallback to the target properties. However, it should be configured the other
way around. Use the target properties first, and fallback to the default_provider
properties second, and fallback to a default value as a last resort.

The properties where this was incorrectly configured were:

  • S3 provider:
    • bucket_name,
    • extract, and
    • object_key.
  • Lambda provider:
    • function_name and
    • input.
  • CodeDeploy provider:
    • application_name and
    • deployment_group_name.

By submitting this pull request, I confirm that you can use, modify, copy, and
redistribute this contribution, under the terms of your choice.

…ider

**Why?**

Allowing a specific parameter file to be used. This is especially useful if you
would like to reuse a template. Often these templates are committed or generated
with another generator than generate_params.py.

**What?**

* Added params_filename to the CloudFormation provider schema.
* Updated the CloudFormation provider to support setting the params_filename.
* Documented the param_filename property in the CloudFormation provider docs.
@sbkok sbkok added the enhancement New feature or request label Dec 12, 2022
@sbkok sbkok added this to the v3.2.0 milestone Dec 12, 2022
Copy link
Contributor

@StewartW StewartW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much nicer, great addition thanks!

@sbkok sbkok merged commit 200fcfe into awslabs:master Dec 14, 2022
@sbkok sbkok deleted the feat/set-param-filename-per-target branch December 14, 2022 07:34
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

Successfully merging this pull request may close these issues.

3 participants