Merging ChatOps and Jobs Capabilities

[jvanderaa]

Often times as we do work, we are setting up work to be done in some fashion that seem to have a strong similarity in code, but different visualization paths. ChatOps and Jobs. Both are often used to do something. I believe that there is a hurdle of some sort of mapping users in Nautobot and Chat users. So bringing here to start the discussion and perhaps find a way to handle this. I don't have a solution on how to solve this idea, and someone else may have a thought on how to do so.

The thought being, set up so that way ChatOps execution is just a Job, with a matter of having different result paths, one that could go to Chat, the other that always is done within the Jobs UI.

[jvanderaa]

As ChatOps and Jobs expands, there could definitely be some code reuse and violations of DRY principals.