feat: Run(API) with different project

[lewyytm]

Hi,
for my purpose I had a two projects (prod and dev) in GCP but dataform repository only on one of them (prod). So when I try to Run API to save queries on dev project then it doesn't work.

So my proposal is to add place to define dataform GCP project location to Run API 😄

[ashish10alex]

Hi @lewyytm , thanks for raising the feature request. Can you try this option please and let me know if this solves the issue ?
I tried it on my own setup and it does seems to work.

[lewyytm]

Not really, before update to newest version it was info with path and that extension doesn't found repository.

Now on the latest version I have errors:

1. 'Error getting git info: Command failed: git rev-parse --abbrev-ref HEAD 'git' is not recognized as an internal or external command, operable program or batch file.'
   Interesting - because I use on VS Code git all time.
2. Error determining git repository and or branch name
   Also interesting because I'm still synchronize local files with git repo.

[ashish10alex]

For the errors :

1. It is using git cli . Is the available. I think you will have it but it's mostly likely not in your windows path when node js is trying to invoke it from vscode. After you have this path issue you will have to restart vscode for it to be able to use git cli from a node process. In earlier versions I was using vscode git extension, but this did not work well if the user was using git wortrees.
2. This can happen if the repository name and the dataform repository name in GCP does not match. You can fix this by using the following setting

[lewyytm]

1. But I have git cli installed and added to windows path:
   PATH:
   C:\Users\lewyytm\AppData\Local\Programs\Git\cmd
   and if I open powershell.cmd and type git then I get response.

[ashish10alex]

I see, I was trying to think of similar issue that an other user had faced where the company blocked powershell usage. Turns out it was you 😅. Could it be because of this ?

[lewyytm]

Hahah yes it was me. So it might be the reason? As you see my git installation is in user local path due to company restriction.
In previous case the workaround was create a npm.bat file in local repo location, but now this trick to create git.bat with path to local git installation doesn't work.
Or maybe this bat should be placed in different place?

[ashish10alex]

I have not faced this restriction myself. So you will have to try a few options. Will be good to consult AI and see what could be the possible things you could try. How are you able to compile the project, dataform cli is also used by the extension which should also be running in powershell . Are you using custom bat file for that too or something else ?

[lewyytm]

Yeah so git.bat is also a solution for that problem - what is very nice. Finally - its work! 😄

Unfortunately, it doesn’t very comfy for me at the moment.
Mainly because I have six different repositories for different projects in my VSCode workspace.
The plugin seems to be written on the assumption that we’re working within a single VSCode window on a single project and a single repo – in that case, it actually works really well: you just set the project and repo variables in the settings once and everything works.

However, when I switch between project x and repo xx and project y and repo yy, I’d have to edit the plugin settings every time – not exactly convenient in my case :) For CLI I only make ctrl+alt+d and change dataform workspace.

[ashish10alex]

I’d have to edit the plugin settings every time

I though this was an issue myself until very recently you can have vscode settings specific to your workspace in .vscode/settings.json file in your workspace. E.g.

This lets me have each repository with its own custom configuration and makes parallel development smother.

wrt to switching between projects. I have a hot key setup which pops ups the projects and I can fuzzy find the one I want to switch to in vscode