BigQuery and AdswerveBigQuery uses a service account in the working directory

[loicmathieu]

Expected Behavior

BigQuery and AdswerveBigQuery uses a service account in the working directory which may not e compatible with all task runner.
We need to find another away.

Actual Behaviour

See https://github.com/kestra-io/plugin-singer/blob/master/src/main/java/io/kestra/plugin/singer/targets/AdswerveBigQuery.java#L157 and https://github.com/kestra-io/plugin-singer/blob/master/src/main/java/io/kestra/plugin/singer/taps/BigQuery.java#L118

Steps To Reproduce

No response

Environment Information

• Kestra Version:
• Plugin version:
• Operating System (OS / Docker / Kubernetes):
• Java Version (If not docker):

Example flow

No response

[anna-geller]

@loicmathieu is this still relevant? asking as I think in the end you and Brian adjusted task runners to inject the full working directory

[Ben8t]

@loicmathieu @brian-mulier-p is it something we can close ?

[brian-mulier-p]

I think the AbstractSinger should take its workingDirectory from the taskRunner for it to work properly.

@loicmathieu I'd suggest that the CommandsWrapper's workingDirectory is instead taken from the taskRunner (same for outputDirectory) and since AbstractSinger takes its wdir from CommandsWrapper it will work, WDYT ?

For @Ben8t @anna-geller I'm pretty sure that it's effectively an issue as-of now (maybe worth doing a test with SA and a taskRunner to check ?)

[loicmathieu]

@brian-mulier-p I have no idea, this needs to be sorted out but we must have a single working directory and not two