You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current generation for compose uses a combination of text/template and a context struct that represents the deployment metadata. We want a more scalable model that reduces the generation context for a given resource and streamlines generation.
Some items on the wishlist:
Default flowing of parameters in the Bicep module
Supporting existing resources references vs. AVM module creation
Support partial synth
It should aim to improve readability, code reviews, and authoring experience. An ideal authoring workflow is the ability to ingest a fully synthesized Bicep into scaffolded generation assets and requires fewer manual tweaks.
The minimum requirements are:
Overall cost of development (author time, review time, validation time) for an addition of 1 resource should be logarithmic with respect to number of resources supported in composability for us to scale. Ideally, it's a constant cost -- but the Bicep module constructs may be the limitation here.
The text was updated successfully, but these errors were encountered:
The current generation for
compose
uses a combination oftext/template
and a context struct that represents the deployment metadata. We want a more scalable model that reduces the generation context for a given resource and streamlines generation.Some items on the wishlist:
It should aim to improve readability, code reviews, and authoring experience. An ideal authoring workflow is the ability to ingest a fully synthesized Bicep into scaffolded generation assets and requires fewer manual tweaks.
The minimum requirements are:
The text was updated successfully, but these errors were encountered: