azure

A 21-post collection

Organizing Azure resources with Tags

Creating a number of resources and organizing them in any software solution can get daunting without some sort of method to your madness. In a project, developers might decide to use logical folder structures or naming conventions based on a framework or what just makes sense. Azure Resource Groups is described as the "logical group" for organizing your items where a group contains all related resources for an application. But what if there is a need to categorize or put multiple labels on each of these resources? For instance, When was the resource created? Who created it? Is it a demo, production, test? Who or what department is the application for? Tags enable this exact functionality. The excerpt from the...


Dipping the toe in the Azure Compute space and then some.

Over the last couple of weeks, I've just skimmed the areas of ARM templates, CLI, Docker on Linux, Azure Functions and AppService Web Apps. Check out these articles and let me know if there is something you'd like to see more on; there's a ton to talk about to solve any solution. dotnet new angular to Azure with Docker using CLI Visual Studio 2017 has been released and the features are great for Windows developers. However along with it comes .NET Core 1.0 tooling and large improvements to the command line experience for macOS and Linux users developing ASP.NET Core applications. One of the prevalent features shown off in VS 2017 is the Docker support and capabilities to...


Serverless like a Superhero with Azure Functions

In my most recent Pluralsight course, I spent some time talking about using Swashbuckle to create documentation for ASP.NET Core WebAPI applications. Swashbuckle is the .NET Core implementation of the OpenAPI Specification aka Swagger, but there are many other open source tools too for other languages. The demo project built was a simple "traditional" ASP.NET Core API that generated a "Superhero Name" based on a FirstName and LastName passed to the GET method. The old API architecture The architecture would not surprise anyone who has seen an MVC structure for ASP.NET Web API projects, except the .NET Core portions. Controllers, Views, Startup.cs, etc., published to an Azure AppService running on IIS. If this were a node....


Use a container to show your function swagger

One option for enabling the Swagger-UI capabilities is to direct the consumers of the api to http://petstore.swagger.io and have them put the url in the box at the top of the page. That's professional right? :-/ Alternatively, you can add the url of the service to the end with ?url= such as http://petstore.swagger.io?url=https://yoursite.azurewebsites.net/docs/swagger.json, but again probably not the best option. Here we can take advantage of Docker here and use the swaggerapi/swagger-ui Docker image and set some ENV variables within an Azure AppService Web Application and accomplish our own SwaggerUI. Creating a new AppService (Linux) Here we will use the Azure CLI to create our...


Unmasking your swagger with proxies in Azure Functions

In my post Testing Azure Functions with Postman and Swagger I showed how to use the API Specification capabilities in Azure Functions and then take the endpoint url and test the API using Postman. Notice the url that is provided for the API. It isn't human readable, nor something I could rattle off to another developer over the phone or easy re-type. Creating a proxy A feature in Azure Function is proxies. Using this feature we can establish a new proxy for our function to point a "nice" url to the "no-so-friendly" API Definition. Now you can share the shorter more reasonable url, even use the test Swagger UI at http://petstore.swagger.io. Be sure to add http://petstore....