Igor Stoyanov Atlassian Team

Also try to run cloudfront via aws cli from your local machine (without using pipe, with using the same creds) to understand where the problem exactly is.

In the meantime, do you know of a Container Image we can use that has the Firestore CLI installed I don't know any official docker images for Firestore CLI.

@Felipe Micheletto just for tests. Set up in cloudfront pipe config aws region like in your s3 pipe config. AWS_DEFAULT_REGION: "us-east-1"

@Jurgen Heeffer . We released a new version 3.4.0 of the pipe: script: - pipe: atlassian/kubectl-run:3.4.0 variables: KUBE_CONFIG: $KUBE_CONFIG KUBECTL_COMMAND: 'apply' RESOURCE_PATH: 'nginx.yml' DISABLE_VALIDATION: 'true' Regards, Igor

@Felipe Micheletto hi. Thanks for your question. We need more information. Please, provide us your config details, and a screenshot of your repository variables (values should be hidden). Alternative way to is to configure some test script in pipeline to check your aws configuration: script: - curl…

@Hiroki Shiotsuka hi. Thanks for your question. Please, check this issue. Maybe there is a whitespace in the KEY value. Seems like the same problem here. Regards, Igor

@Ronak Toshniwal hi. Thanks for your question. Check this guide: image: node:10.15.0 pipelines: default: - step: name: Build and test script: - npm install - npm test branches: staging: - step: name: Clone script: - echo "Clone all the things!" Regards, Igor

@Quintonn Rothmann hi. Thanks for your question. FILES_IGNORED feature available from version 1.2.0: script: - pipe: atlassian/git-secrets-scan:1.2.0 variables: FILES_IGNORED: 'package-lock.json' Regards, Igor

@Larry Johnson hi. We will try to release a new version from few days to 3 weeks. Regards, Igor

Hi @Larry Johnson . Thanks for your feedback. Yes, seems like this i bug according to your investigation. We will dive deep into this this and notify you about results. Regards, Igor

--dry-run is used in validate spec file by default, and i guess you receive spec file validation failed error. Our team may think about disable validation with an option available for user, will be this solution ok for you?Regards, Igor

@Jurgen Heeffer Thanks for your response. Please provide also your pipeline output. Regards, Igor

Hi @David Valero . Check this example: script: - pipe: atlassian/ftp-deploy:0.3.7 variables: USER: my-ftp-user PASSWORD: $FTP_PASSWORD SERVER: 127.0.0.1 REMOTE_PATH: /tmp/my-remote-directory from ftp-deploy pipe mentioned above. Although, check this guide with alternative tool usage. Regards, Igor

Hi there, we will investigate this feature request and notify you. Regards, Igor

Hi @Jurgen Heeffer . Thanks for your question. Please provide us your configuration details of how you use the pipe. Maybe you use the pipe this way: script: - pipe: atlassian/kubectl-run:3.3.1 variables: KUBE_CONFIG: $KUBE_CONFIG KUBECTL_COMMAND: 'apply' RESOURCE_PATH: 'nginx.yml' KUBECTL_ARGS: - '--dry-run' then you…

Hi @Eragaraju, Nandini . Alternatively, you could check jenkins-job-trigger pipe, maybe this pipe might cover your cases. Regards, Igor.

@Kenichi Ogawa hi. Sorry for late response. Our team released a new version of google-cloud-storage pipe 1.2.0 where we fix issue with DEBUG variable. Regards, Igor

@Will Chan hi. You can check your authorization process locally with simple python script: import requests import json def api_call(): response = requests.get( url, auth=(username, password) ) print(json.loads(response.text)) if __name__ == '__main__': api_call() username is the name…

@Vladimir Vlach hi. Thanks for your feature request. We will investigate this and notify you. Regards, Igor

@Jorge Cuarón hi. Please specify more details of how you want to use this pipe. What is your case? Regards, Igor

@AZZ hi. Thanks for your question. According to the blog post you should use pipe like this: pipelines: default: - step: name: delete cache if changes in the build dependencies script: - pipe: atlassian/bitbucket-clear-cache:3.1.1 variables: BITBUCKET_USERNAME: $BITBUCKET_USER_NAME BITBUCKET_APP_PASSWORD:…

@Christopher Hill hi. We released new version 0.4.0 of the checkstyle-report pipe including changes according to your PR. Regards, Igor.

@Javier Martín hi. We released a new firebase-deploy pipe version 3.0.0 with firebase-tools 11. Regards, Igor

@Shaik Naina hi. Reference to Bitbucket API repository. Also if you need to copy repository to s3, we recommend you to use aws-s3-deploy pipe. script: - pipe: atlassian/aws-s3-deploy:1.1.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: 'us-east-1'…

@Kenan Hussein hi. Thanks for your question. Unfortunately, ftp-deploy does not support ssh keys. But we have a lot of alternatives with using ssh-keys. You may try: * rsync-deploy * sftp-deploy * scp-deploy Regards, Igor

@Christian Kuenne hi. Thanks for your question. If you could understand which files are changed, then pass only this files to artifacts (not all). To verify what files was changed you could try to use Bitbucket API commits. Regards, Igor

@Asad hi , Thanks for your question. You docker image is set in your infra/k8s/billing-dep.yaml file, is this true? `the pipeline starts and build a docker image, then pushes the image to the AWS ECR` -- maybe instead of latest tag provide some custom tag (exact version of latest image) ? And than update your yaml…

@Will Marsman hi. Thanks for your suggestion. To cover your case check this reference of how to attach file. Regards, Igor

@anusha reddy hi . Thanks for your question. You can add DEBUG to see more detailed output. Also before pipe execution you can execute ls -lat to see if in the step with pipe you have your files. Also check that you provide build/libs/*.jar in artifacts, but your source is just build/libs/Application.jar maybe problem…

@John Kreisher hi. 401 means you can't pull from your private AWS Registry. You should determine in which step this error occurs. Please, provide detailed logs output, maybe I can help you. Regards, Igor