Added a web ui to render intended configurations

[gsnider2195]

This is a web ui wrapper for the REST API implemented in #824

UI Light mode

UI Dark mode

Nav menu

Docs

[itdependsnetworks]

Just thinking out loud.. can we make this not required and if not set figure out what the default git repo is this device is?

[itdependsnetworks]

In the majority of cases, I don't think people will need to switch this.

[bryanculver]

Because different devices can have different golden config settings, and different golden config settings can have different git repositories, we would have no way of showing the user in this view what repo was used to generate the template.

Either:

• They would have to back-solve which golden config setting applied and then which git repository
• We will have to enhance the API response to provide more information than it does today

[smk4664]

Should we not also check permissions for GoldenConfig? If I am not mistaken, a user would need to have view permissions for Golden Config in order to see the Intended Configuration.

Suggested change

	permission_required = ["dcim.view_device", "extras.view_gitrepository"]
	permission_required = ["dcim.view_device", "extras.view_gitrepository", "nautobot_golden_config.view_goldenconfig"]

[gsnider2195]

I could see a user wanting to require a permission to use this but I don't think view_goldenconfig is the correct permission. Perhaps we need to implement a new permission similar to run_job?

[gsnider2195]

Implemented feedback:

• Add a <strong> tag to the form to make it more apparent that this is for development purposes
• Put in bold in helper text that the git repo is synced on hitting the render button
• Remove gitrepository from the input and use the default for the device
• Open a FR to core to implement checking out an arbitrary branch to a temporary location - Clone a GitRepository to a temporary location nautobot#6487
• Open a FR in GC to add the branch field to this UI - Add branch to generate-intended-config API #828