Oleksandr Kyrdan Atlassian Team

Hi @Leonardo Medici , Thank you for your question! With version 1.0.0 we migrate aws-cli to v2. Pipe based on docker image amazon/aws-cli:2.2.13. This version is not officially released yet, but thank you for sharing your case. Good explanation. If you ok we'll ask you some more details soon about this case. We're…

Hi @Breno Thank you for your question! Yep, it looks like a bug. We'll fix it and release a new version and notify you. Best regards, Oleksandr Kyrdan

Hi @Luke Way Thank you for your question! Yep, it looks like a bug. We'll fix it and release a new version and notify you. Best regards, Oleksandr Kyrdan

Hi @sachinthasankalpa Thank you for your question! It's a good case to use ssh-run pipe, so you could run a command or a bash script on your server ) script: - pipe: atlassian/ssh-run:0.3.0 variables: SSH_USER: 'ec2-user' SERVER: '127.0.0.1' SSH_KEY: $MY_SSH_KEY MODE: 'script' COMMAND: 'myscript.sh' # path to a script in…

@Ryan Hinton , We'll discuss and investigate this feature with a team and notify you. Also, it would be great if you create a new suggestion request with type Suggestion and Component: Pipelines - Pipes. So, other people could vote for your feature too. Thank you for your feature request! Cheers, Oleksandr Kyrdan

Hi @Ryan Hinton , Thank you for your question! It's a good case for rsync-deploy pipe: Rsync is famous for its delta-transfer algorithm, which reduces the amount of data sent over the network by sending only the differences between the source files and the existing files in the destination. script: - pipe:…

Hi @Vincent D , Thank you for your question! As you could discover in the browser, UI uses the next url to generate ssh-keys pair: curl -X POST -H "Content-Type: application/json" https://api.bitbucket.org/internal/repositories/{workspace}/{repo}/pipelines_config/ssh/key_pair/generate response will returns public key that…

Hi @Cord Slatton , Thank you for your question! We're investigating this issue and will notify you about updates. Cheers, Oleksandr Kyrdan

Hi @Reethu , Thank you for your question! It would be nice if you could share with us more details about your case: logs, pipelines configuration, etc. Cheers, Oleksandr Kyrdan

Hi @Francis Poulin , Thank your for your question! We're investigating this issue and notify you. Cheers, Oleksandr Kyrdan

Yep, pipes automate routine repetitive tasks.

Ok, it's good to use AWS Serverless Application Model (AWS SAM) to init lambda. Just init sam app: sam init also, available options: -r, --runtime [python2.7 | ruby2.5 | ruby2.7 | java8 | python3.7 | dotnetcore2.0 | nodejs10.x | nodejs12.x | nodejs14.x | dotnetcore2.1 | dotnetcore1.0 | python3.6 | go1.x]

@[deleted] yep, but provide us with real example of BODY_PLAIN text, please, so we'll try to find a root cause.

Hi @Himanshu Thawait , Thank you for your question! It would be nice if you provide us with more details, pipeline configuration and logs about this case to help you. Cheers, Oleksandr Kyrdan

Hi @Châu Nguyễn Trung , Thank you for your question! We provided atlassian/slack-notify pipe where you could modify "pretext" and "text" sections in a payload of your slack message with PRETEXT and MESSAGE variables: - pipe: atlassian/slack-notify:1.0.2 variables: WEBHOOK_URL: '<string>' PRETEXT: '<string>' MESSAGE:…

Hi @Jinkle Pancholi , Thank you for your question! It's a good point to start with a ready to use template npm-publish example that we created for you. It would be nice if you provide us with more details about your experience. Cheers, Oleksandr Kyrdan

Hi @Luis Plaza , Thank you for your question! It would be nice if you provide us with details about BODY_PLAIN variable context. Cheers, Oleksandr Kyrdan

Hi @Eduardo de Vila Thank you for your question! Currently the pipe support only deploy command. Other commands you could run directly with the heroku cli. Cheers, Oleksandr Kyrdan

Hi @Max Howarth , Thank you for your suggestion! It's a good idea to extend examples for the pipe. We'll notify you about this update. Cheers, Oleksandr Kyrdan

Hi @basvdijk , Thank you for your question! We have tested examples provided in the YAML anchors guide and overrides works good, where variable NAME setup in different deployments (test, development, production): definitions: steps: - step: &build-test name: Build and test script: - echo "Build and test" - step: &deploy…

Hi @Douglas Kolpien Thank you for your question! We'll investigate this feature and notify you. Cheers, Oleksandr Kyrdan

Hi @finnruijter , Thank you for your question! Instead providing a port with the server to the SERVER variable. Provide it as an EXTRA_ARGS: script: - pipe: atlassian/sftp-deploy:0.5.7 variables: USER: 'ec2-user' SERVER: '127.0.0.1' REMOTE_PATH: '/var/www/build/' LOCAL_PATH: 'build' DEBUG: 'true' EXTRA_ARGS: '-P 2222'…

Hi @Rahul Arora Thank you for your question! It could be a good case for the new feature OpenID Connect provided by Bitbucket Pipelines: Deploy a new version of your CloudFormation stack with OpenID Connect (OIDC) alternative authentication without required AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY. Parameter oidc: true in…

Hi @radim Thank you for your question! Could you provide more details with us about attach file case? We'll investigate the feature and notify you. Cheers, Oleksandr Kyrdan

Hi @Rémi Mercier , Thank you for your question! We'll investigate the feature and notify you! Cheers, Oleksandr Kyrdan

Hi @Andy Osborn Thank you for your finding. We'll fix this soon. Cheers, Oleksandr Kyrdan

Hi @Tarek Abdel Sater , As we investigated: to support immutable AWS ECR and re-running builds you could provide build with unique tags by passing TAGS parameter: script: # build the image - docker build -t my-docker-image . # use the pipe to push to AWS ECR - pipe: atlassian/aws-ecr-push-image:1.3.0 variables:…

Hi @heister82 , Thank you for your question! There is the Configure bitbucket-pipelines.yml page with all needed info and links. There are two ways to configure your pipeline: you can either directly write the YAML file or you can use the UI wizard provided by Bitbucket. The Get started with Bitbucket Pipelines guide will…

Hi @Vitor Oliveira A new version of the serverless-deploy pipe released. Big updates provided: updated the Serverless Framework to 2.* version and NodeJS to 12 LTS version. script: - pipe: atlassian/serverless-deploy:1.0.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY It…

Hi @Anthony Tsoi , We have added support for Python serverless-python-requirements. A new version of the serverless-deploy pipe released. Also, updated NodeJS to 12 LTS version and the Serverless Framework to 2.* version. script: - pipe: atlassian/serverless-deploy:1.0.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID…