Answer accepted by question author
Hi @Stuart Wepener ,
Most of the Blueprint resourcing is going towards Template Specs (video overview) and Deployment Stacks, which is what Blueprints are eventually going to use under the covers. For authoring improvements, focus is bicep. The GA (General Availability) ETA is set for March/April when the new underlying resource types (template specs and deployment stacks) are ready and we can migrate everything over.
More info in this talk:
Most of the Blueprint UserVoice asks are either already implemented in Templates/Template Specs, or they are something we will address with above mentioned future improvements to templates/bicep and stacks.
Lastly, even though the Blueprint service is listed as βPreviewβ, we treat the service as GA, which means even once a migration path is made available, we will continue to support the current Blueprint APIs for 1-3 years or until everyone has been migrated.
-
Niraj P 1 Reputation point
We are using Blueprints heavily in our Prod env, do u think after migration to Biceps we can still support prod. Can we remain in BP or have to move to Biceps to get support in long run?
-
Rajesh Swarnkar 1,236 Reputation points
Simply Put can you please quote a rough timeline.
-
Jay Freeman 11 Reputation points
Look on youtube for deployment stacks. It is in preview and is amazingly easy with bicep https://youtu.be/6Cmz5ESdkCM
Sign in to comment
