4 ms·

I mostly agree with you, but on this one: > Difficult to assess what's going to be a replacement (other than browsing the doc) Do you know of any better solu

by pugz 6y ago

I mostly agree with you, but on this one: > Difficult to assess what's going to be a replacement (other than browsing the doc) Do you know of any better solution than docs? Or better implementations of docs? I struggle to imagine how they could handle this better - but I've been using CF for so long that my imagination is limited.

bassman9000 6y ago
I'd be happy if they just showed: - the nested stack elements that are going to change, not only the parent ones - the logical members/fields that prompt the change from the changeset window. All this info they have, and should be trivial to show, which tells me they either don't use their own tooling (no dogfooding), or they have internal, better diagnostic tools not exposed to customers.
- wgjordan 6y ago
  > the nested stack elements that are going to change, not only the parent ones You should be pleased to hear that 'change sets for nested stacks' support was just released last week: https://aws.amazon.com/about-aws/whats-new/2020/11/aws-cloudformation-change-sets-now-support-nested-stacks/ https://aws.amazon.com/about-aws/whats-new/2020/11/aws-cloud... https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/change-sets-for-nested-stacks.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
  - bassman9000 6y ago
    Nice! Thanks. For others like me who were wondering why we didn't see this change: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/change-sets-for-nested-stacks.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui... create-change-set – Change sets for nested stacks is not enabled by default for the AWS CLI. To create a change set for the entire stack hierarchy, specify the --include-nested-stacks parameter. For more information, see To create a change set (AWS CLI). Edit: grammar.

by pugz 6y ago

bassman9000 6y ago

I'd be happy if they just showed: - the nested stack elements that are going to change, not only the parent ones - the logical members/fields that prompt the change from the changeset window. All this info they have, and should be trivial to show, which tells me they either don't use their own tooling (no dogfooding), or they have internal, better diagnostic tools not exposed to customers.

wgjordan 6y ago
> the nested stack elements that are going to change, not only the parent ones You should be pleased to hear that 'change sets for nested stacks' support was just released last week: https://aws.amazon.com/about-aws/whats-new/2020/11/aws-cloudformation-change-sets-now-support-nested-stacks/ https://aws.amazon.com/about-aws/whats-new/2020/11/aws-cloud... https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/change-sets-for-nested-stacks.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
- bassman9000 6y ago
  Nice! Thanks. For others like me who were wondering why we didn't see this change: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/change-sets-for-nested-stacks.html https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui... create-change-set – Change sets for nested stacks is not enabled by default for the AWS CLI. To create a change set for the entire stack hierarchy, specify the --include-nested-stacks parameter. For more information, see To create a change set (AWS CLI). Edit: grammar.