Scopes are logical grouping which in turn can have multiple environments and resources underlying. All these can be grouped to represent an organisational hierarchy.
- The user is provided with a default parent scope initially, under which they can create multiple scopes.
- A scope can inherit environments from its parent scope.
- The scope icon has different colours
- Red - Represents there are unassigned physical resources in the scope, the number of unassigned resources also shown with that.
- Orange - Represents there are unassigned logical resources in the scope
- Green - Represents the resource assignment is complete i.e. all the logical resources have physical resources in all its environment.
- The scopes can be added, moved, edited and deleted.
- Moving a scope will move all the scopes below it to the new destination.
- Deleting a scope will delete all the scopes below it.
- To obtain an overview of the particular scope a summary tab is provided under which user can get details on different metrics in numerical count and pie charts to represent physical and logical resources.
In the tree structure of scopes, different environments can be set depending upon the company's use. It may be Dev/Test/Prod or more complex. This structure can be inherited down the tree. The result is each resource is also allocated to an environment.
- To create a new environment, click on the Create button provided in the top right corner.
- When the user moves into the environment tab, they will be provided with an option called Inherit Environments from Parent Scope under each scope, by enabling it in child scopes user can inherit the newly created environment from parent scopes.
- User can view assigned resources, by clicking on the view icon, add resources to the environment, edit and delete using the four action icons.
- When you move into Add Resources, all the unassigned resources under that scope will be listed. You can select them and assign them to the respected environment.
- When viewing the resources, an option to remove it from the environment is also available.
While dealing with dev/test/production scenario there will be multiple similar resources. They are just the dev/test/production versions of each other. In Resource Map we provide a way to indicate that the physical resources are different instances of the same logical resource.
All the mapped and unmapped resources in the scope will be displayed here with the corresponding resource group, type, subscription, environment and logical resource.
By using the Assign button you can assign the physical resource to the specific environment and logical resource.
Resources can be remapped to other scopes by clicking on the Remap button.
You can unmap the resources from the scope by clicking on the Unmap option.
If any unavailable resources are present, you will be indicated with an icon along with the count of unavailable resources, next to Assign button and a symbolic representation next to the unavailable resource.
Resources can be manually assigned to a scope. The relevant logical resource can also be created and mapped to an environment. By assigning these resources user can get a comparison view of its properties in one place.
To create a logical resource, click on the Create Logical Resource button and go ahead with creation.
After creating the logical resource, the corresponding resource type and the environments under that scope will be generated dynamically.
If you click on the add icon under the environment column, the physical resources with the same resource type as a logical resource that is assigned to the selected environment or not assigned to any environment will be displayed as a dropdown.
- If the environment doesn't have resources under that resource type then it will display as 'No resources found'.
- You can assign the resource to that environment and get back to the resource assignment column and you will be listed with resource added to the environment and the unmapped resources under that scope.
- After mapping the resources, the logical resource name becomes clickable.
- By clicking on it you will get a comparison view between the mapped resources.
- These resources might originate from different resource groups and subscriptions but its properties can be viewed in one blade.
- With the help of user management, you can restrict or provide access to the user. Admin and Superuser will have access to the entire resource map section and all the scopes. Custom users can be given access only to particular scopes along with reading and manage permissions.
- To provide access or restrict a user initially create a custom role and under the Resource Map section enable the scopes that you permit the user to work on.
- After this, the user will not be able to view or access the other scopes.