Adding resources ourselves

[daniel-rogers-gh]

Hi there,

Thanks for your efforts on this tool, it's pretty neat.

It seems not uncommon to want to add some resource type, is there a way we can do this safely which won't break if those resources are added later?

I can see the resources json has an id field which is incremented - if I add my own resource blocks and set ids that start from a much higher number (say 2500) would this be ok? Then if the same type is added, I can remove my custom one.

Additionally, if we straight up delete the resources we don't use is that ok or will this cause issues with later upgrades and it's recommended to just disable them?

Thanks again.

[BryanSoltis]

Thank you for the feedback. Herea re some details for the items you noted:

1. Adding resource types
   The tool is not configured to allow adding a resource type to the configuration, by default. These values are derived from Azure resources and their Max/Min properties are very unique for each type.

You can enable "Resource Type Editing" in the Admin/Site Settings section, which allows you to add your own Resource Types. Please review the information/links, as this could potentially cause issues with the tool if not done properly.

For the ID, this is a value that is dynamically generated when the resources are added. The real unique keys are the resource and short name** values. This is how the tool actually matches things on the backend.

We will occasionally update the resource types. The tool is designed to have this type of update be independent than a code change. The Configuration Page will prompt Admins to update if a new version of the resource types is released. In the Configuration Page / Resource types/ Configuration section, you will see an option to update the local resource types with the latest version with some options. I would recommend backing up any details prior to this to ensure you don't lose any custom data.

2. Deleting Resources

The tool is designed to allow resource types to be disabled, meaning they will not be available for selection. You can delete them, as well (if you have the above setting configured). Deleting should not affect functionality, however, if you refresh the data from the GitHub repo, any deleted resource type would be restored.

You can "Refresh" your resource type data (which pulls the latest version from the GitHub repo) or you can "Reset" your resource type data (which resets it to your original installation version).

Hope this help.
Bryan

[daniel-rogers-gh]

Thanks for such a quick reply! Ahh, I forgot about that setting - I think that will do for now, thank you.

If anyone else comes along the guidance was here: https://github.com/mspnp/AzureNamingTool/wiki/Resource-Type-Editing