Application Composer Issues

[paul-uz]

• Parameters not supported
• Mappings not supported
• Conditions not supported
• Removes parameters added manually in the YML
• Doesn't handle !Ref's in properties box for resources like HostedZone, have to keep redoing them manually

Example above, you can see how the !Sub function is used in the YML, is bastardised in the Composer settings window.

[ccaum]

Thanks, Paul. On the parameters being removed from the template, can you describe the steps you go through to reproduce this? We suspect this might be caused by not saving changes made directly to the template and then making changes in the canvas. To be clear, you should be able to this, but we want to make sure we understand what's triggering it.

[paul-uz]

I'll have to try and recreate it step by step but I'm pretty sure it'd happen even after saving the template.

What's interesting is it would leave one parameter alone, despite one of the removed ones being used as a !Ref target.

[Zizaco]

The fact that Application Composer removes comments is very annoying

[JLargent42]

We rolled out a fix to how we're handling parameters that should address the problem you were facing.

We've also updated our template parsing logic, so comments are better preserved now.

Thanks for the feedback, paul-uz and Zizaco!