I’m pretty sure @techwatching.bsky.social will frame this post and hang it on a wall, you’ve made a friend happy 🤗
I’m pretty sure @techwatching.bsky.social will frame this post and hang it on a wall, you’ve made a friend happy 🤗
Last blog post of the year: how I use ytt with my @home-assistant.io configuration.
For what I can recall I have used them for naming resources, and manipulating configuration stored in a json file.
Also it’s a way to declare “global” variables without putting them in a module or passing them as parameter in every module.
Terraform is a safe bet but Bicep is evolving very nicely.
Let me share a blog post like my friend @techwatching.bsky.social just did: blog.xmi.fr/posts/terraf...
😇
I second user-defined types, and want to quote user-defined functions as a second vote 🤓
Snippet of the following Bicep code: // This will return the tenant id of the subscription // where the managed application is being deployed var customerTenantId = subscription().tenantId // This will return the tenant id from where the // managed application was published var publisherTenantId = tenant().tenantId
Quick #azure #bicep tip I have learnt when working on an Marketplace Managed Application: it turns out that tenant().tenantId and subscription().tenantId doesn't return the same value when working in a cross-tenant situation 🤓