Andrew Wilson's Blog

{ ... Plan - Architect - Develop - Reflect - Improve - Repeat ... }

Bicep | File Reference in a Git Repository Containing Spaces

Problem Space I recently started working on a Git Repository (not of my own creation) that had a repository name containing spaces. As a helping hand when a repository is created with spaces in the name, the spaces are replaced with %20 when cloned … Unless otherwise specified, however, this would then need to be specified whenever another user/pipeline clones the repo. See the git command below: git clone https://.../.../my%20repo myrepo My best practice answer would be, don’t create repositories with names containing spaces, but this one already did.

Azure Storage Account | Deletion and Reuse

Problem Space When it comes to creating Azure Storage Accounts, the name has some very important rules that need to be kept in mind. These rules will not only be important in the creation of the resource, but will be critical in deletion and reuse. The rules are as follows: Storage account names must be between 3 and 24 characters in length and may contain numbers and lowercase letters only.

Azure API Management | Product Required Subscription Behaviours

Background | Functional Workings of APIM Subscriptions Subscriptions are a nice and easy method of securing your APIs in APIM, however as I bumped into a small detail around their use the other day, I thought it wise to note it down. Azure API Management Subscriptions operate at three scope levels: All APIs Applies to any API that requires a Subscription. As this will allow access to ANY api, use this with caution.

Azure API Management | Subscription Contract Names

Problem Space Subscriptions are a nice and easy method of securing your APIs in APIM, however as I bumped into a small detail around their use the other day, I thought it wise to note it down. When a Subscription Key is required on an API, as an invoker I will need to provide either a Header or a Parameter to my request which will contain the Subscription Key. By default:

Bicep File Template | VS Code Snippet

Problem Space: After developing native ARM templates for a year or two within a set structure, I have found myself applying the same structure to my Bicep templates using comments. This structure however is not setup by default, and in actuality, the sequencing of your bicep components doesn’t really matter as long as your dependencies are there. Of course we typically follow the standard pattern as shown below, but the larger the template the harder it is to see the breaks between.