Project Radius - Rios Engineer

rios.engineer

Open WebUI on Azure: Part 1 - Architecture & Deployment - Rios Engineer

rios.engineer

GitHub - johnlokerse/azure-bicep-mcp-integration-setup: 💪 Guidance on how to use the Azure Bicep MCP server to integrate with Claude, Codex, LMStudio and more tools!

💪 Guidance on how to use the Azure Bicep MCP server to integrate with Claude, Codex, LMStudio and more tools! - johnlokerse/azure-bicep-mcp-integration-setup

github.com

Rate limiting Entra External ID Email OTP Events with APIM - Rios Engineer

rios.engineer

Automating Azure Bicep Testing with Ephemeral Environments in GitHub Actions - Rios Engineer

rios.engineer

GitHub - riosengineer/cloudflare-bicep-deploy: A CloudFlare Bicep Local Deploy extension to deploy DNS records to CloudFlare & more.

A CloudFlare Bicep Local Deploy extension to deploy DNS records to CloudFlare & more. - riosengineer/cloudflare-bicep-deploy

github.com

#azure #azurebicep #biceplang #azuredeploymentstacks #infrastructureascode | Dan Rios

𝗔𝘇𝘂𝗿𝗲 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗰𝗸𝘀 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗼𝗿? 𝗖𝗵𝗲𝗰𝗸 𝘁𝗵𝗶𝘀 𝗼𝘂𝘁. I’ve been working on an idea around an Azure Deployment Stacks orchestrator recently. It’s got a bit of a Terragrunt inspired foundation, but tai...

linkedin.com

Create your own custom extension for Azure Bicep

A long-lived dream of many Azure Bicep users has been the ability to deploy outside the Azure environment, similar to what you can do with Terraform. With the experimental Bicep local-deploy featur…

johnlokerse.dev

UK Community Awards – Microsoft Technology UK Community Recognition Awards

ukcommunityawards.co.uk

Build a Custom Extension for Bicep

In a previous post about Bicep Local, I explained how this feature enables the creation of custom extensions that can be used directly within Bicep. Also that by using this option you are not limited ...

msftplayground.com

My favourite 5 Bicep resources - Rios Engineer

rios.engineer

Release v0.38.3 · Azure/bicep

Highlights onlyIfNotExists GA! (#17996) @onlyIfNotExists() resource onlyDeployIfNotExists 'Microsoft...' = { name: 'example' location: 'eastus' properties: { ... } } [Experimental] ...

github.com

GitHub - riosengineer/cloudflare-bicep-deploy: A CloudFlare Bicep Local Deploy extension to deploy DNS record to CloudFlare & more.

A CloudFlare Bicep Local Deploy extension to deploy DNS record to CloudFlare & more. - riosengineer/cloudflare-bicep-deploy

github.com

From the AzureBicep community on Reddit

Explore this post and more from the AzureBicep community

reddit.com

Using Shared Variable File Pattern to simplify Azure Roles In Bicep - Rios Engineer

rios.engineer

GitHub - riosengineer/Bicepify: Simplify getting started with Bicep through easy to digest examples🦾

Simplify getting started with Bicep through easy to digest examples🦾 - riosengineer/Bicepify

github.com

Integrating Companies House with Azure AI Agent in Foundry Using OpenAPI - Rios Engineer

rios.engineer

Sign Up | LinkedIn

500 million+ members | Manage your professional identity. Build and engage with your professional network. Access knowledge, insights and opportunities.

linkedin.com

Sign Up | LinkedIn

500 million+ members | Manage your professional identity. Build and engage with your professional network. Access knowledge, insights and opportunities.

linkedin.com

Create your own Bicep Local Extension using .NET

Bicep Local Deploy can be used to author Bicep files which use Bicep extensions that are designed to run fully locally, without the need for an Azure connection. This quick start guide provides guidance for creating your own Bicep Local Extension using .NET. For more information on Bicep Local please check out this doc and this demo. This guide assumes you have the .NET 9 SDK installed locally, and the Bicep 0.37.4 (or higher) CLI and VSCode extension installed. Project Scaffolding Create a project file named MyExtension.csproj with the following contents:<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <RootNamespace>MyExtension</RootNamespace> <AssemblyName>my-extension</AssemblyName> <IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract> <PublishSingleFile>true</PublishSingleFile> <SelfContained>true</SelfContained> <InvariantGlobalization>true</InvariantGlobalization> <TargetFramework>net9.0</TargetFramework> <Nullable>enable</Nullable> <ImplicitUsings>enable</ImplicitUsings> <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath> <AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath> </PropertyGroup> <ItemGroup> <PackageReference Include="Azure.Bicep.Local.Extension" Version="0.37.4" /> </ItemGroup> </Project> Create a file named Program.cs with the following contents: using Microsoft.AspNetCore.Builder; using Bicep.Local.Extension.Host.Extensions; using Microsoft.Extensions.DependencyInjection; var builder = WebApplication.CreateBuilder(); builder.AddBicepExtensionHost(args); builder.Services .AddBicepExtension( name: "MyExtension", version: "0.0.1", isSingleton: true, typeAssembly: typeof(Program).Assembly) .WithResourceHandler<MyResourceHandler>(); var app = builder.Build(); app.MapBicepExtension(); await app.RunAsync(); 3. Create a file named Models.cs with the following contents: using System.Text.Json.Serialization; using Azure.Bicep.Types.Concrete; using Bicep.Local.Extension.Types.Attributes; public enum OperationType { Uppercase, Lowercase, Reverse, } public class MyResourceIdentifiers { [TypeProperty("The resource name", ObjectTypePropertyFlags.Identifier | ObjectTypePropertyFlags.Required)] public required string Name { get; set; } } [ResourceType("MyResource")] public class MyResource : MyResourceIdentifiers { [TypeProperty("The resource operation type", ObjectTypePropertyFlags.Required)] [JsonConverter(typeof(JsonStringEnumConverter))] public OperationType? Operation { get; set; } [TypeProperty("The text output")] public string? Output { get; set; } } 4. Create a file under Handlers/MyResourceHandler.cs with the following contents: using Bicep.Local.Extension.Host.Handlers; public class MyResourceHandler : TypedResourceHandler<MyResource, MyResourceIdentifiers> { protected override async Task<ResourceResponse> Preview(ResourceRequest request, CancellationToken cancellationToken) { await Task.CompletedTask; return GetResponse(request); } protected override async Task<ResourceResponse> CreateOrUpdate(ResourceRequest request, CancellationToken cancellationToken) { await Task.CompletedTask; request.Properties.Output = request.Properties.Operation switch { OperationType.Uppercase => request.Properties.Name.ToUpperInvariant(), OperationType.Lowercase => request.Properties.Name.ToLowerInvariant(), OperationType.Reverse => new([.. request.Properties.Name.Reverse()]), _ => throw new InvalidOperationException(), }; return GetResponse(request); } protected override MyResourceIdentifiers GetIdentifiers(MyResource properties) => new() { Name = properties.Name, }; } Publishing your extension locally Run the following to in the project directory to publish your extension to your local filesystem: dotnet publish --configuration release -r osx-arm64 . dotnet publish --configuration release -r linux-x64 . dotnet publish --configuration release -r win-x64 . bicep publish-extension --bin-osx-arm64 ./bin/release/osx-arm64/publish/my-extension --bin-linux-x64 ./bin/release/linux-x64/publish/my-extension --bin-win-x64 ./bin/release/win-x64/publish/my-extension.exe --target ./bin/my-extension --force Running your extension Create a file named bicepconfig.json with the following contents: { "experimentalFeaturesEnabled": { "localDeploy": true }, "extensions": { "myextension": "./bin/my-extension" }, "implicitExtensions": [] } 2. Create a file named main.bicep with the following contents: targetScope = 'local' extension myextension param inputText string resource foo 'MyResource' = { name: inputText operation: 'Reverse' } output outputText string = foo.output 3. Create a file named main.bicepparam with the following contents: using 'main.bicep' param inputText = 'Please reverse me!' 4. Run the following: bicep local-deploy main.bicepparam You should see the following output in your terminal: % bicep local-deploy main.bicepparam Output outputText: "!em esrever esaelP" Resource foo (Create): Succeeded Result: Succeeded Giving feedback and getting help Bicep Local is still under development and your feedback is critical to shaping the feature. Please use our GitHub Repo to get support for give feedback.

techcommunity.microsoft.com

linkedin.com