-
Notifications
You must be signed in to change notification settings - Fork 38
1.6.1 error on !GettAtt of Outputs - was passing with 1.6.0 #149
Comments
Apparently, the issue does not occur prior to 1b867f1, perhaps @martysweet or @tomdionysus can help more... FWIW, I've just tested with:
|
This was caused by #139 (@tomdionysus) - Attributes are now checked and then assigned. I should have thought of more edge cases this could have affected. As we don't know the outputs to a CFN::Stack this is an edge case which was missed. Unfortantly the AWS::CloudFormation::Stack resource from AWS Spec doesn't mention anything about its Attributes or potential attributes.
The simple (and probably only) fix would be to add a bypass for this resource type, like in the following link. The CFN Spec doesn't give enough information to say there might be custom attributes for this type.
Making this type customisable is a future improvement, the above fix will resolve the issue for now. I am happy to accept a patch for this (and test cases) and make a new release asap, if not I will fix and release this evening (GMT). |
Thanks @RazzM13 for the quick fix. @gidbalugo The fix should now be up in npm as version v1.6.2, please can you confirm everything is working again? |
Sweet!! That fixed it. Thanks @martysweet @RazzM13 |
Oops - cheers guys. My bad. |
@tomdionysus No worries! |
We recently failed on 1.6.1 update which produces error on
!GetAtt
Outputs of AWS::CloudFormation::Stack. This was passing on before the update of 1.6.1Sample template code causing failed results on 1.6.1 update but with passing build with 1.6.0
Error
The template(s) resulting to error(bootstrap.yaml)
The
Outputs
part of source template.Thanks
The text was updated successfully, but these errors were encountered: