When issuing a token with the sdfcli how is the token stored. I issued a token with the VS Code NetSuite SDF extension, and deploying SDF projects works great. But I would like to push a file not part of an SDF project using uploadfiles command of the sdfcli. How can I communicate to sdfcli when using uploadfiles to use the token I assume it already knows about that was saved via the VS Code SDF extension

I imagine the

sdfcli

manages tokens separately from the VSCode extension. I don't think the VSCode extension is 'official' from NetSuite?

Yeah it’s not official but I thought since it seems to be using the Cli it would allow me to reuse the token already generated. Having to enter the password isn’t that bad.

curious: are you on a mac?

yes I am

i think you already got the answer before, but sdf in general stores tokens in the .clicache file (in the same folder as the sdf cli .jar file)

the new nodejs cli is supposed to improve on that, coming very soon supposedly.

@battk I apologize I was certainly expecting the cache being present to provide token type deployment from VS Code and the command line to the same account, but I wasn't seeing that. I have re-issued a new token with the issuetoken command via the SDF VS Code extension and now the command line uploadfiles works using the same token. Given both the SDF Extension and the command line sdfcli (with password prompt) was working with the same sandbox, email, url, account number I'm not sure what I had done wrong on the token side but re-issuing the token has fixed the issue.