Some users insist on overwriting an existing tag when publishing their modules to the registry. If they want to immediately validate or consume the module they will have to either run force restore or delete the existing module from the cache.
We have the ability to link two webapps together via the service plan, but there should be an overload that can take in one web app to link to another e.g.
A set of Azure Templates for getting you started in Azure with Fortinet solutions. This repository is a place for beta releases and work on the latest templates to be published on github.com/fortinet or custom templates.
This code allows you to load any existing Azure Data Factory project file (*.dfproj) and perform further actions like "Export to ARM Template" or to debug custom C# activities
The Landing Zone architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
.Net Core 2.1 C# with React Starter Project that provides Identity Authentication and Authorization using JWT. Based on .NET Core JavaScriptServices Spa React + Redux using TypeScript. Additional support available for Docker and ARM Templating. Project uses Key Vault for secrets and EntityFrameworkCore to migrate Identity tables.
Some users insist on overwriting an existing tag when publishing their modules to the registry. If they want to immediately validate or consume the module they will have to either run force restore or delete the existing module from the cache.
Should we do it for them automatically?