Mariog2000/azure-mapper-pro-visual-cloud-architect

"I need to create an app that can export resources in Azure Subscriptions and create the diagrams in Visio and eventually other free diagramming tools. This would ideally have the initial option to first identify and map out the Hub and Spoke setup (assuming present), or if there were 2 Hubs for example, 1 for WAF and 1 for a core Firewall that also acts as the Hub for on-prem connectivity (via ExpressRoute or VPN GW, etc). Ideally I'm able to treat this like a REAL application so that it's very secure but also not overly complex. This may mean users would have the option to use controls like being setup with or to use an App Registration or SPN or Managed Identities but also have the flexibility to use user credentials to run the tool (assuming proper permissions). Before we start, since this isn't always very responsible, please first break down the build process into logical sections so that I have the necessary blocks of code to make this a reality. I also want to create a POC to ensure functionality so I want to first start with functionality before adding the finishing touches meaning, we can wait on setting up the ability to use traditional identities and start with my own credential. Here are the functional requirements I'd like to create: 1. Each Resource should include the Azure Resource Name and Resource type along with details that would be valuable for troubleshooting such as IP addresses, DNS names, URL's, relevant data depending on the type of resources (i.e., if a FW should include FW details, a Load Balancer should include traffic flow details, NSG should include configured Rules, UDR's should contain routing details, etc.). It should include an Image related to the Resource Type and also a way to change that image. The image should also be a clickable-link so that users can click on the image and it would bring them directly to the resource. 2. Each Resource needs to have an understanding of all the resources it can connect to and any other resources that can connect to it. This should be designed in a way that makes it possible to create data-flow diagrams that show primarily how 2a. traffic coming from the internet would traverse into the resource, 2b. traffic from on-prem would traverse to the resource, and 2c. how traffic would traverse to the resource from elsewhere in the Azure Tenant. 3. As part forthe export of the Azure resources, there should also be additional services or tools that allow identifying how resources operate. For example, perhaps a script or query or executable could reside in a Hub or Spoke resource to "ping" resources if the "availability" of a given resource can't be determined but other tools, information, configurations, name resolution or routing info, or logs. 3a. If other services are required to verify effective routes or if a resource can be reached across multiple VNET's or through FW's or other challenges that may be limited by identities, certificates, etc., those resources should be as an optional requirement of the application. 3b. It should not be a requirement that other Subscriptions need to have any changes or added resources for this software to work to prevent any types of interference to Production workloads. 3c. However, if there are certain types of resources or configurations that could greatly increase the ability to troubleshoot or identify details important to the overall creation of an effective visual design of Azure Tenant as a whole and/or any individual Subscriptions, please create a way to notify the users of these features, their requirements to work, and what value they could provide if setup/configured. 4. There should be some sort of GUI or at least a CLI so that this doesn't just look like a bunch of scripts. But there should also be an option to just execute code or a series of scripts for environments with limited options to install software like secure govt sites. 4b. For options that only allow executables to run, clear details on exactly how to run the commands, the pre-reqs needed to complete to ensure the right permissions have been granted, the location to be running the code from, the terminal type, etc., real examples of how to run the commands so users don't have to guess the syntax, the location the output will be stored, and any next-steps to perform after the commands/tools have been executed. 5. The output of the Azure Resource export AND the output from any tools should all be stored in a format that's fast, free, and allows for the data to be aggregated in a way that's easy to retrieve. 5b. The data should be able to help first determine how to create a connectivity map of the resources, broken down by Tenant, Management Group, Subscription, VNET, Resource Group, etc. 5c. The data should also be able to be reported on to simplify determining details like Cost Summaries or other ways to group data like by TAGS or by Resource Type, or by Application Names, etc.. 5d. The data should also be able to provide useful network, security, exposure, routing, certificate, and other types of data to allow users to quickly get a summary of for example "list all resources that are internet-facing" or "show all resources exposed directly to the internet without a Firewall or WAF in front of them", etc. 6. The Resource Icons/Images should allow a user to mouse-over the Resource to expose primary resource info like name, IP address, port/protocol, etc. 6b. There should also be a no-frills option to see the list of exported data and for each Resource, create an easy view of all the Resources that are "Upstream" and "Downstream" resources. That way a user could trace if or how Resources are accessible from for example, the Internet, from on-prem, or other Subscriptions if network Peering is setup. Overall, this tool needs to act as a network mapping tool that creates the visual aides to both see and troubleshoot connectivity issues with options to figure out a variety of other details about the environment at a quick glance. "Please word this prompt in a way that will make it much easier for an LLM to understand my request and get as close as possible to a 1-click prompt to create the application all in one-shot. TRY HARD! Here's the data I need fixed --> "I need to create an app that can export resources in Azure Subscriptions and create the diagrams in Visio and eventually other free diagramming tools. This would ideally have the initial option to first identify and map out the Hub and Spoke setup (assuming present), or if there were 2 Hubs for example, 1 for WAF and 1 for a core Firewall that also acts as the Hub for on-prem connectivity (via ExpressRoute or VPN GW, etc). Ideally I'm able to treat this like a REAL application so that it's very secure but also not overly complex. This may mean users would have the option to use controls like being setup with or to use an App Registration or SPN or Managed Identities but also have the flexibility to use user credentials to run the tool (assuming proper permissions). Before we start, since this isn't always very responsible, please first break down the build process into logical sections so that I have the necessary blocks of code to make this a reality. I also want to create a POC to ensure functionality so I want to first start with functionality before adding the finishing touches meaning, we can wait on setting up the ability to use traditional identities and start with my own credential. Here are the functional requirements I'd like to create: 1. Each Resource should include the Azure Resource Name and Resource type along with details that would be valuable for troubleshooting such as IP addresses, DNS names, URL's, relevant data depending on the type of resources (i.e., if a FW should include FW details, a Load Balancer should include traffic flow details, NSG should include configured Rules, UDR's should contain routing details, etc.). It should include an Image related to the Resource Type and also a way to change that image. The image should also be a clickable-link so that users can click on the image and it would bring them directly to the resource. 2. Each Resource needs to have an understanding of all the resources it can connect to and any other resources that can connect to it. This should be designed in a way that makes it possible to create data-flow diagrams that show primarily how 2a. traffic coming from the internet would traverse into the resource, 2b. traffic from on-prem would traverse to the resource, and 2c. how traffic would traverse to the resource from elsewhere in the Azure Tenant. 3. As part forthe export of the Azure resources, there should also be additional services or tools that allow identifying how resources operate. For example, perhaps a script or query or executable could reside in a Hub or Spoke resource to "ping" resources if the "availability" of a given resource can't be determined but other tools, information, configurations, name resolution or routing info, or logs. 3a. If other services are required to verify effective routes or if a resource can be reached across multiple VNET's or through FW's or other challenges that may be limited by identities, certificates, etc., those resources should be as an optional requirement of the application. 3b. It should not be a requirement that other Subscriptions need to have any changes or added resources for this software to work to prevent any types of interference to Production workloads. 3c. However, if there are certain types of resources or configurations that could greatly increase the ability to troubleshoot or identify details important to the overall creation of an effective visual design of Azure Tenant as a whole and/or any individual Subscriptions, please create a way to notify the users of these features, their requirements to work, and what value they could provide if setup/configured. 4. There should be some sort of GUI or at least a CLI so that this doesn't just look like a bunch of scripts. But there should also be an option to just execute code or a series of scripts for environments with limited options to install software like secure govt sites. 4b. For options that only allow executables to run, clear details on exactly how to run the commands, the pre-reqs needed to complete to ensure the right permissions have been granted, the location to be running the code from, the terminal type, etc., real examples of how to run the commands so users don't have to guess the syntax, the location the output will be stored, and any next-steps to perform after the commands/tools have been executed. 5. The output of the Azure Resource export AND the output from any tools should all be stored in a format that's fast, free, and allows for the data to be aggregated in a way that's easy to retrieve. 5b. The data should be able to help first determine how to create a connectivity map of the resources, broken down by Tenant, Management Group, Subscription, VNET, Resource Group, etc. 5c. The data should also be able to be reported on to simplify determining details like Cost Summaries or other ways to group data like by TAGS or by Resource Type, or by Application Names, etc.. 5d. The data should also be able to provide useful network, security, exposure, routing, certificate, and other types of data to allow users to quickly get a summary of for example "list all resources that are internet-facing" or "show all resources exposed directly to the internet without a Firewall or WAF in front of them", etc. 6. The Resource Icons/Images should allow a user to mouse-over the Resource to expose primary resource info like name, IP address, port/protocol, etc. 6b. There should also be a no-frills option to see the list of exported data and for each Resource, create an easy view of all the Resources that are "Upstream" and "Downstream" resources. That way a user could trace if or how Resources are accessible from for example, the Internet, from on-prem, or other Subscriptions if network Peering is setup. Overall, this tool needs to act as a network mapping tool that creates the visual aides to both see and troubleshoot connectivity issues with options to figure out a variety of other details about the environment at a quick glance. "

initial commit