You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to programmatically enter the credentials for a google cloud connection via the cli interface? Two issues arise when I enter from the command line prompt.
First, I have to get an authentication key from Google. Even though I have connected via CyberDuck to the same server, with the same credentials, I am asked for a key. Can this be retrieved from a keychain?
Second, I have to enter the project id at a prompt. With regard to this second issue, what is the format to put the project id into the server string?
I currently use gs://bucket-name/ and the error I get is
Listing directory / failed. Invalid argument. Unknown project id: 0. Please contact your web hosting service provider for assistance.
I believe anything after the last slash will be thought of as a folder. Can I enter a project id on the same line?
Please advise
I am running 6.3.1.27192
The text was updated successfully, but these errors were encountered:
Is it possible to programmatically enter the credentials for a google cloud connection via the cli interface? Two issues arise when I enter from the command line prompt.
First, I have to get an authentication key from Google. Even though I have connected via CyberDuck to the same server, with the same credentials, I am asked for a key. Can this be retrieved from a keychain?
Second, I have to enter the project id at a prompt. With regard to this second issue, what is the format to put the project id into the server string?
I currently use gs://bucket-name/ and the error I get is
Listing directory / failed. Invalid argument. Unknown project id: 0. Please contact your web hosting service provider for assistance.
I believe anything after the last slash will be thought of as a folder. Can I enter a project id on the same line?
Please advise
I am running 6.3.1.27192
The text was updated successfully, but these errors were encountered: