Oleksandr Kyrdan Atlassian Team

Hi @Sam Mahr A new version of serverless-deploy pipe is released: - pipe: atlassian/serverless-deploy:2.0.0 changes: 2.0.0 * major: Breaking changes. Refactored pipe to support better auth logic and major providers AWS, GCP, AZURE. * minor: Add OIDC support for AWS provider. Add support for AWS_OIDC_ROLE_ARN variable. *…

Nice! Thanks for your feedback! 👍

@Sam Mahr Also, make sure that all dependencies (package/tools ) in your project support the latest version of Python. Some, quick investigation for the Serverless Framework v3 cases for python3.11 and python3.12. There could be some gap between language/platform release and other ecosystem upgrade. So, python:3.11 should…

@Sam Mahr the pipe's base docker image moved to python:3.11-slim. Could you try it and provide a feedback?

@Sam Mahr please, pay attention that pipe's docker image based on python:3.11-slim. Looks like you try to spawn python3.10 instead.

Hi @Sam Mahr Could you try the new dev version of the pipe with Poetry in the pipe's base docker image before the release and share feedback: - pipe: docker://bitbucketpipelines/serverless-deploy:1.5.0.163-dev

@Sam Mahr Thank you for your question! The pipe's base docker image contains only base dependencies to keep the image thin. There are many variety of dependencies all around the users projects. If you need extra dependencies according to your project, pipe supports preexecution script. Additionally, check if the version of…

Hi @Jamshaid Thanks for your question! For your case we have renovate-scan pipe. Just add to you bitbucket-pipelines.yml file the next: script: - pipe: atlassian/renovate-scan:0.5.0 variables: CONFIG_FILE_PATH: '<your-config.yaml>' To start using this pipe you need to create a Bitbucket account for Renovate bot usage.…

Yep, good idea. For the custom prompt - Have you tried MESSAGE variable. Content of the message object to extend system prompt. If provided, users MESSAGE will extend default pipe’s messages. 

Hi @Yuriy Berdnikov Thanks for the detailed feedback and contribution to the community. Yep, it's a bug. We have fixed and released a new version of the bitbucker-chatgpt-codereview pipe: atlassian/bitbucket-chatgpt-codereview:0.1.2 Welcome you feedback or feature request! Best regards, Oleksandr Kyrdan

Hi @Yuriy Berdnikov Thanks for your question! It would be nice if you could share your configuration from the bitbucket-pipelines.yml and extended logs of the pipe execution. Best regards, Oleksandr

Hi @sudhakar Thanks for your question! Try to pass the next extra args instead: SCAN_EXTRA_ARGS: - "--fail-on=high" Best regards, Oleksandr Kyrdan

@Peter Boling It would be nice if you could provide some details and examples of the solution and share your experience with the Atlassian community Write an Article. Let's make Bitbucket Pipes better! Best regards, Oleksandr Kyrdan

Hi @Sam Mahr Thanks for your question! You could use any runtime supported by cloud platform: Multi-Language - Supports Node.js, Python, Java, Go, C#, Ruby, Swift, Kotlin, PHP, Scala, & F# Best regards, Oleksandr Kyrdan

Hi @Peter Boling Thanks for your feedback. It is a good feature case to contribute to the open-sourced pipe to make it better. Any pull-request with a new features or improvements from the community are welcome (How to Contribute to the pipe). Best regards, Oleksandr Kyrdan

@Fulvio Nigrisoli Your error relates to AWS resources setup. So, try to extend permissions. Best regards, Oleksandr Kyrdan

@Tharinda Hashen Thanks for your question! Please, provide us with logs about your issue. Best regards, Oleksandr Kyrdan

Hi @Peter Boling Thanks for your question! If you want substitutes the value of environment variable $WORK_LOG into payload file, you should have template file, i.e. payload.json.template with name of the variable you want to invoke "$WORK_LOG" after command executed envsubst < "payload.json.template" > "payload.json" you…

Hi @Abinaya Abi Thanks for your question! Try to add DEBUG variable to email-notify pipe to see more details about your error: script: - pipe: atlassian/email-notify:0.13.1 variables: ... DEBUG: "true" Best regards, Oleksandr Kyrdan

Hi @Fulvio Nigrisoli Thanks for your question! Please, provide us with more details about this case: * bitbucket-pipelines.yml file * logs output of the pipeline's build Best regards, Oleksandr Kyrdan

Hi @Andrea Calderon Thanks for your question! Currently, the azure-web-app-deploy pipe supports only zip files: - step: name: "Build and test" script: - npm install - npm test - zip -r my-package-$BITBUCKET_BUILD_NUMBER.zip . artifacts: - my-package-*.zip- step: name: "Deploy to Azure" script: - pipe:…

Hi @Javier Diez Thank you for your question! In the newest version pipe supports passing explicit version of the lambda function. So, please, follow the example Combining Update with Alias of the README.md. Make shure that after pipe execution with command "update" you fetch new version from the file…

Thank you for sharing feedback with the community.

Hi @michal.koval A new pipe's version with updates and fix is released: atlassian/azure-aks-helm-deploy:3.2.0 with the next updates: * bump mcr.microsoft.com/azure-cli:2.56.0 * bump and pin kubernetes v1.29 * add kubelogin v0.1.0 Best regards, Oleksandr Kyrdan

Hi @Patrick Comes The new version of the pipe is released: script: - pipe: atlassian/email-notify:0.13.1 variables: FROM: 'myemail@example.com' TO: 'example@example.com' HOST: 'smtp.gmail.com' DISABLE_AUTH: true Best regards, Oleksandr Kyrdan

Hi @Patrick Comes Thanks for your contributions to the community. It is a bug, we'll fix it and notify you. Best regards, Oleksandr Kyrdan

Hi @michal.koval The new feature released: pipe supports AZURE_LOGIN_NON_INTERACTIVE variable. script: - pipe: atlassian/azure-aks-helm-deploy:3.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_AKS_NAME: $AZURE_AKS_NAME AZURE_RESOURCE_GROUP:…

Hi @Krzysztof Sierszeń Thank your for your question! It could be your case to use FORCE_NEW_DEPLOYMENT variable: Whether to force a new deployment of the service. Default: false. Use this option if you need to trigger a new deployment with no service definition changes: if your updated Docker image uses the same tag as…

Hi @Thirukumaran Kubendran We released a new version of the pipe with logging of revision version: script: - pipe: atlassian/aws-ecs-deploy:1.10.1 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: 'us-east-1' CLUSTER_NAME: 'my-ecs-cluster' SERVICE_NAME:…

Hi @Mohammad Sharabati In additional to the previous answer about bash required for the pipe. It's better way to put commands you want to execute into file myscript.sh and use MODE script: script: - chmod 005 myscript.sh - pipe: atlassian/ssh-run:0.7.1 variables: SSH_USER: 'ec2-user' SERVER: '127.0.0.1' MODE: 'script'…