search

aws / aws-cli

Universal Command Line Interface for Amazon Web Services
Other
15.46k stars 4.1k forks source link

Packaging of AWS::CloudFormation::Stackset resource using AWS CLI clouformation package command #8663

Closed nafiuyakubu closed 5 months ago

nafiuyakubu commented 5 months ago

Describe the feature

The feature request proposes extending the functionality of the AWS CLI's cloudformation package command to support packaging templates specifically designed for AWS CloudFormation StackSets.

Currently, the package command excels at packaging regular CloudFormation templates that might reference local artifacts like Lambda function code or API Gateway definitions. However, it lacks the ability to handle StackSet templates directly.

Feature request breakdown:

Target audience: AWS users who deploy infrastructure using CloudFormation StackSets. Desired functionality: The cloudformation package command should be able to process StackSet templates. Ideally, it would:

  1. Recognize the AWS::CloudFormation::StackSet resource within the template.
  2. Handle any specific requirements for packaging StackSet templates (if applicable).

Use Case

Scenario:

An organization manages infrastructure across multiple AWS accounts and regions using CloudFormation StackSets. They currently deploy their StackSets by manually uploading the template to S3 and then referencing it in a separate StackSet template. This process is cumbersome and requires managing two separate templates.

Problem:

The current workflow requires additional steps for uploading the template to S3 and managing separate templates for the StackSet configuration and resources. It can be error-prone to maintain consistency between the two templates.

Proposed Solution

The aws cloudformation package command could be extended to support packaging CloudFormation StackSet templates. This would involve:

  1. Recognizing the AWS::CloudFormation::StackSet resource within the template.
  2. Including the StackSet template itself in the packaged output, potentially alongside any referenced artifacts like Lambda functions.

Other Information

No response

Acknowledgements

CLI version used

AWS CLI version 2

Environment details (OS name and version, etc.)

Linux

tim-finnigan commented 5 months ago

Thanks for the feature request and sharing your use case. The team is already tracking this request here: https://github.com/aws/aws-cli/issues/5590, so I will close this as a duplicate. This feature request is still under consideration but not prioritized at this time. In the meantime, you should be able to use the SAM CLI to address your use case.

github-actions[bot] commented 5 months ago

This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.