Git push/pull of Query Info

## EPIC Description

From customer interviews, we have learned that at least 1 customer maintains their queries in a text file and then cut and pastes into the Cloud UI when they need it\. They maintain versioning and "master" query list this way\.

Versioning of query information and management of it within the Cloud UI has been brought up as a topic of discussion that is still pending\. However, an alternative view point was raised, stating that if a developer is using it and they already have git as their versioning mechanism, why would they want versioning in the software\.

Still, in this scenario they are cutting and pasting from git\. The idea here would be to eliminate that cut and paste and allow for a git repo location to be used for pulling the influx script to be shown in the UI and creating a PR when finished \- along with the corresponding client library code that we can generate for them also being able to be linked up to a different area of the repo where they store their query functions\.

## Business Justification

There may not be any as this idea needs validated before any further consideration\.

## Source

Alex Boatwright with the idea of keeping versioning in git \- just added on it with the copy and PR functions on top of it\.

Others, mainly internal folks have asked about this