Skip to main content

Preventing accidentally resource deletion - Lock Resource | Azure

A week ago, one of our team member modified a script that clean (removes) Azure resources, based on a naming convention. Because the number of our Azure Subscription is limited, the Development Team is sharing the same subscription between them and for DEV and TEST environment.
To be able to have a control on resources and trace the owner of them we have:
  • Naming conventions: A prefix that specify the owner of the resource or the environment

    • rvteststorage (rv - Radu Vunvulea)
    • dv (Dev Environment) 
    • tt (Test Environment)
    • ...
  • Azure Resource Groups that give us the possibility to group resources together.
As we can see in the above diagram, Azure Resource Groups can be used with success to group together different resources that have a logic for your application or from a business perspective. 

Coming back to the initial cleaning script, there was a small bug in the script, that didn't took into account the prefix of Azure Resource Groups and removed all the resources that were under that subscription. 

Now, the questions is what we can do to avoid  this kind of things in the future. Of course, multiple subscriptions would be great, but this will not happen. A review of the script from another team member would work also, but not all the time there will be time for things like this and bugs like this cannot be seen each time.

How nice it would be to have a flag on our resources, that would not allow anybody to remove (delete) the resources. This features exist on AWS for some time and wait.... we forgot that from last year we have a similar feature on Azure also. 
This feature is called "Resource Lock" and allows us to lock a resource for deletion. People will be able to modify it, but as long as this flag is set, nobody will be able to delete this resource. In this way we can avoid in the future situations like this.
This lock can be set not only when we create the resource, but also after it and can be used for any time of resource. The Lock can be set using Power Shell by specifying LockLevel flag to 'CanNotDelete' of using ARM.

Power Shell
$resourceGroup = 'devenv'
$storageAccountName = 'devlogstorage'

New-AzureResourceLock -LockLevel CanNotDelete '
-LockNotes 'Delete is not allowed for DEV env storage' `
-LockName 'DevEnvStorageLock' `
-ResourceName $storageAccountName `
-ResourceType 'Microsoft.Storage/storageAccounts' `
-ResourceGroup $resourceGroup -Verbose

More information about this feature can be found on Azure page:


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…