At the moment, CLI operations and the GitHub Sync modules rely on the same API for pulling and deploying workflow artefacts (state.json and project.yaml). This is okay until a TB user (on core plan) needs to push data from their local instance to TB. There are a few options here:
Use the token to differentiate the use case (if the tokens are separate) or adding a flag to distinguish the use cases.
Make provisioning available only on growth and scale plans of TB. In this case, the user will be able to pull but will not be able to deploy from their computers to TB.
At the moment, CLI operations and the GitHub Sync modules rely on the same API for pulling and deploying workflow artefacts (state.json and project.yaml). This is okay until a TB user (on core plan) needs to push data from their local instance to TB. There are a few options here:
cc: @taylordowns2000 @stuartc @josephjclark