can anyone tell me what is the KEY_FILE variable that has to go in this:
i have a
private_key_id
&
private_key
script:
- pipe: atlassian/google-cloud-storage-deploy:0.4.0 variables:
KEY_FILE: $KEY_FILE
PROJECT: 'my-project'
BUCKET: 'my-bucket'
SOURCE: '.'
tried all sort of thing on this now and nothing gets it working, i get this output:
i've tried adding a path to the file, no go
i've tried adding a variable, pasting the whole json file into it = no go
i've tried adding a variable, pasting the private_key_id into it = no go
there must be someone on these borads that knows about this, its a atlassian repohttps://bitbucket.org/atlassian/google-cloud-storage-deploy/src/master/
If i remember it correctly, the key_file was the content of that json in base64 encoded.
ok, so i have to take the json file and run it through a base64 encoder? then upload that file to the repo, and point $KEY_FILE to that with a "variable"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://bitbucket.org/atlassian/google-cloud-storage-deploy/src/master/pipe/pipe.sh
->
echo "${KEY_FILE}" | base64 -d >> /tmp/key-file.json
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks very much, i think i have it working now properly, another question would be, is there a way to add google cdn cache invalidation to this, as in if a file changes , it invalidates the cache as well. not 100% sure yet if google auto invalidates it or not, need to test more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i see one problem here already, it seems to upload the whole file, not just the files that have changed, where as if i do a "transfer from S3 to google bucket" it only transfers the files which have changed. that in the long run will save a load of money etc and it auto invalidates the "changed" files, as a new date stamp on them
Is there anyway to only upload 'changed' files?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I get stuck with KEY_FILE variable now. Do u know how to define it ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@davidstanton @minhkha7911 I'm facing the same issue. how did you fixed?
I already have integrate my KEY_FILE to a repository variable with base64, but when I run, I get the same message as you.
I have this step in my YML:
- step:
name: GCP Storage
script: - pipe: atlassian/google-cloud-storage-deploy:0.4.5 variables:
KEY_FILE: $KEY_FILE
PROJECT: 'my-project'
BUCKET: 'my-bucket'
SOURCE: 'the path with the APK'
(of course I have other configurations on my YML but I copy only the part to GCP STORAGE)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@davidstanton I'm facing the same issue. how did you fixed?
I already have integrate my KEY_FILE to a repository variable with base64, but when I run, I get the same message as you.
I have this step in my YML:
- step:
name: GCP Storage
script: - pipe: atlassian/google-cloud-storage-deploy:0.4.5 variables:
KEY_FILE: $KEY_FILE
PROJECT: 'my-project'
BUCKET: 'my-bucket'
SOURCE: 'the path with the APK'
(of course I have other configurations on my YML but I copy only the part to GCP STORAGE)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.