Initiating Nautobot jobs

[MeganerdDev]

Closes: #223

What's Changed

• Adds init_job subccomand which initiates a Nautobot job by job name

Remaining work

• The acceptance criteria of this PR would require mapping of the username of the user interacting with the chatbot to the username of the user in Nautobot
• The render markdown is incomplete, the present output is a placeholder
• Add supporting subcommand: get_jobs
• Add to documentation

TODO

• Explanation of Change(s)
• Added change log fragment(s) (for more information see the documentation)
• Attached Screenshots, Payload Example
• Unit, Integration Tests
• Documentation Updates (when adding/changing features)
• Outline Remaining Work, Constraints from Design

Notes

• Tested to be working from ChatOps+Mattermost but must statically set the user the job runs as
• Adding a parameter for the user is possible but seems non-preferred solution
• We could also initiate jobs from API, but the ORM makes more sense?

[MeganerdDev]

Also, I used init_job since the run_job namespace is already being used by core, and changing the import run_job as something_else seemed like bad practice.

[MeganerdDev]

@smk4664 @jvanderaa

[smk4664]

We now have the ability to get the Username of the Nautobot user from the chat platform in Next-2.0. Would you mind refactoring this against next-2.0? It would also be nice to ensure the user has permission to run jobs, and limit the list of jobs to jobs they have access to.

[MeganerdDev]

I moved the base for the merge to next-2.0

[MeganerdDev]

I need to test this to confirm working as expected! I followed the pattern I believed was proper however.

I am blocked by an issue getting my homelab up for testing this. Does this look like user error for my homelab?
I am on Chatops next-2.0 branch (3.0.0rc1) with Nautobot v2.0.0rc3
To rule out nautobot as the issue I ran migrate, post_upgrade, collectstatic

[MeganerdDev]

Hi @smk4664, I updated and tested this feature on #270 to be working (outside of some noted edge cases)

I was having some GIT troubles rebasing this to next-2.0 properly and didn't have the time to fit GIT. Hope that is okay! I modified the fragment and all.

[MeganerdDev]

closed in favor of #270