Igor Stoyanov Atlassian Team

@Garth Wood . Working with Lambda container images : To create a Lambda function from a container image, build your image locally and upload it to an Amazon Elastic Container Registry (Amazon ECR) repository. Then, specify the repository URI when you create the function. Regards, Igor

Yes, and i suggested you to update your lambda with aws-lambda-deploy pipe using image you pushed to ecr. I don't know the reason why do you have this issue. I provide you a workaround of how you could update your lambda function. script: - pipe: atlassian/aws-lambda-deploy:1.8.2 variables: FUNCTION_NAME:…

@François Collins . Thanks for your question. We will investigate your case. Regards, Igor.

@Garth Wood hi. Thanks for question. Some of the example of how to build (and deploy) docker image inside a pipeline: step: script: # build the image - docker build -t $IMAGE_NAME:$IMAGE_VERSION -t $IMAGE_NAME:latest . - docker save --output my-docker-image.tar.gz $IMAGE_NAME services: - docker artifacts: -…

@Mike Howarth _Administrator_ hi. Don't know exactly how to solve your initial problem. But have you tried to use Bitbucket Pipes for Azure? Maybe some of them will cover your case. Regards, Igor

hi @Fernando Muller . I think the reason for error is that you have a whitespace (ASCII character space %20) at the end of your DistributionID variable name. Compare the logs with links in pipe versions: === 0.6.0: E99NMDMBH9B99R%20 DEBUG: Sending http request: <AWSPreparedRequest stream_output=False, method=POST,…

@Daniel Carrington hi. Maybe you could split your file to two files, first file will contain only variables that should be ignored and you will exclude it from scan, and the second file will contain all other standard variables that you will scan. Regards, Igor

@[deleted] hi. Take a look at the get commit Bitbucket Cloud REST API. Regards, Igor

@Dryden Linden-Bremner hi. Sorry for the late response. We released a new version of the pipe 3.5.0 that allows to use pre-execution scripts to install all needed plugins: script: - echo 'script logic' > .my-script.sh - chmod 005 my-script.sh - pipe: atlassian/kubectl-run:3.5.0 variables: KUBE_CONFIG: $KUBE_CONFIG…

I don't know, but you could check this case without pipe usage with just sending post requests.

@Steve Annett hi. Thanks for your question. According to docs: The text for the block. This field accepts any of the standard text formatting markup when type is mrkdwn. The minimum length is 1 and maximum length is 3000 characters. So this is a Slack API limit. Regards, Igor

@Scott Mankowitz hi. Thanks for your question. According to pipe README: S3_BUCKET: S3 bucket name or path-like directory structure. LOCAL_PATH: Local path to folder to be deployed. Please, add more details if this is not what are you looking for. Regards, Igor

@John Crawford hi. There is no equivalent to https://github.com/microsoft/azure-devops-symbols in bitbucket pipelines. However, you could try to use azure cli and write your custom solution in bitbucket pipelines. In example: pipeline-artifacts with azure-cli. script: - pipe: atlassian/azure-cli-run:1.1.0 variables:…

@Ricardo Souza pipeline and pipe are different things. In your example you send variables from the pipeline to the pipe via this code: - pipe: atlassian/aws-ecs-deploy:1.0.6 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION…

@Ricardo Souza . Thanks for your question. According to schema - pipe: atlassian/aws-ecs-deploy:1.7.0 variables: AWS_ACCESS_KEY_ID: '<string>' # Optional if already defined in the context. AWS_SECRET_ACCESS_KEY: '<string>' # Optional if already defined in the context. AWS_DEFAULT_REGION: '<string>' # Optional if already…

Hi @[deleted] . Our team released new version of the google-app-engine-deploy 1.2.0 pipe. Docker image google cloud sdk changed from slim to default and also updated to the latest version. Regards, Igor

@Neethu Philip , @Steffen Opel _Utoolity_ , @Sam Ware hi. We released a new version 0.16.0 of the pipe, where we added support to store cloudformation outputs into artifacts. Example: script: - pipe: atlassian/aws-cloudformation-deploy:0.16.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY:…

@74bit please, check this answer, maybe this is your case. Regards, Igor

Hi @Neethu Philip, @Sam Ware . From my current investigation, the only response we have according to create-stack, update-stack is: { 'StackId': 'string' } Is this what you want to be passed as results into the next steps? Regards, Igor

@Param Ramanan hi. Thanks for your question. Check the indentation and also change Script -> script. Example: script: - pipe: atlassian/azure-web-apps-deploy:1.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_RESOURCE_GROUP: $AZURE_RESOURCE_GROUP…

@[deleted] hi. So , you confirmed that required component is not presented in slim image. We will think how to properly fix this problem, and notify you when new release will become available. For now you could use 1.1.0 version, since this version fits your requirements. Regards, Igor.

Hi @[deleted] . To understand your issue, please, provide your bitbucket-pipelines.yml config file. The difference between 1.1.1 and 1.1.0 pipe version is docker image changed to slim: https://bitbucket.org/atlassian/google-app-engine-deploy/pull-requests/30, maybe your required component is not presented in slim image.…

Hi @74bit . This pipe uses under the hood scp command. Please check generated by pipe scp command: is this command correct? Also you may try to execute it without pipe usage to understand where is the problem. Regards, Igor

Could you try to test it without self.hosted runner to understand where is the problem? I just run default pipeline and all is ok.

@Genevieve Awa hi. Also you could try to use jenkins-job-trigger pipe, which allows you to trigger jobs from pipelines. There is also a guide of how to setup pipelines for specific branches . Maybe combining this two guides should help you to solve you problem. Regards, Igor

@oboe_ada hi. There is an example of simple bash pipe Dockerfile. Try this one. Regards, Igor

@RaghavaV hi. It is hard to help you with your initial problem. But maybe some tips that could help you. Try this approach to deploy to AWS with OIDC . Also we have some AWS based pipes, that allows you to deploy to different Amazon services: aws-cloudformation-deploy , aws-code-deploy , aws-ecs-deploy ,…

@Amirull Yusuf Zulkarnain hi. To update previous answer. Seems like the folder that you want to upload is empty. Maybe you need to upload with artifacts. Check this article for more info. Regards, Igor

@James Pinkster hi. Does there exist a somewhat generic Bitbucket Pipe that wraps the AWS CLI v2 command and includes the OIDC authentication options? -- I think the answer is no. Pipes are the small wrappers, that's allow you to automate some common works, but not the full support like boto3 package for aws cli. Full list…

@Christof Koegler _Gaims GmbH_, @Daniel Hilgarth hi. A new version of the pipe released, that should fix this issue: https://bitbucket.org/atlassian/bitbucket-pipe-release/src/5.3.2/ Waiting for your feedback. Regards, Igor