We encountered an issue recently where AMIgo was reporting a recipe as unused, when it actually was in use but via a launch template rather than a launch configuration.
This PR should prevent that from happening again by adding launch template support to AMIgo - so that when it checks whether a bake is in use, it will also check for usages within launch templates.
How to test
I tested this on AMIgo CODE against Prism CODE (with this branch https://github.com/guardian/prism/pull/918) by adding an AMIgo CODE AMI to a launch template and checking that the usage is picked up by AMIgo
What does this change?
We encountered an issue recently where AMIgo was reporting a recipe as unused, when it actually was in use but via a launch template rather than a launch configuration.
This PR should prevent that from happening again by adding launch template support to AMIgo - so that when it checks whether a bake is in use, it will also check for usages within launch templates.
How to test
I tested this on AMIgo CODE against Prism CODE (with this branch https://github.com/guardian/prism/pull/918) by adding an AMIgo CODE AMI to a launch template and checking that the usage is picked up by AMIgo