Normally there are questions and tutorials about using github "workflow action" yml files for deploying ARM templates. I need the opposite capability. For example, if I create an Azure App Service (or Azure static website) using an ARM template, a "workflow action" file will be auto-generated and added to the github repo that I referenced within the ARM template.
That "reverse" behavior is fine, but I want to have some control over the workflow yml file that the ARM template is implicitly creating or using. This is because I am building an Azure "Managed App" (which will eventually become an Azure Marketplace offering)...which requires the entire build/deploy be handled from an ARM template(s). Furthermore, I need the auto-generated "workflow" yml file to be customized to include an Entity Framework (EF) data migration.
In short, when deploying an Azure App Service from an ARM template, how can I influence the auto-generated github workflow actions to incorporate EF database migrations?
The option to simply modify the github workflow activity after it is created, isn't what I'm lookin for.
