TWolversonReply
commented
2 weeks ago We have a couple of use cases where we deploy Logic Apps and Functions with API Management, where the APIM operations need the Lapp/Function trigger URLs with their deploy-time generated keys to set up the backend. APIs are resources deployed by Bicep, so they would come first, except that on first provision the URLs they need don't exist yet, so we have had to run a separate deployment using az deployment group create to provision the API and retrieve the function key in that deployment
We have also used a hook to run Entity Framework migrations.
seesharprun
Background and context
We now have over 100 templates and many more applications using
azdto deploy to Azure. We can see that developers use thehooksfeature to accomplish many things. In order to understand the patterns and to help developers accomplish their goals faster, with less work, and more consistency, we want to understand the common use cases and patterns in how developers usehooks.Once we understand the demonstrated needs, we will use that data to make creating an
azdtemplate or azd-ifying an application more straightforward with less scripting. This might mean new coreazdfeatures, a shared library or package manager for commonhooks, reusability guidelines, and refactoring our documentation.Some common use cases and patterns we see today are:
This is not a complete set. To find the classes of
hookswe will do a combination of qualitative and quantitative customer research to come to a "top 3" list of the most common things we see template authors do.Gather data
Programmatic script
Things we want to learn from the quantitative analysis:
hooksper templateCustomer survey
Things we want to learn from the customer input:
Retrospective observation narrative
Next steps
After we've gathered more data, we will determine the top 3 things we see developers do when authoring a template or azd-ifying their application. We will then decide the best way to approach the solution.