Halyna Berezovska Atlassian Team

@Mary Sipple in the second case you're using right url with / (https://api.bitbucket.org/2.0/repositories/workspace/repo/pipelines_config/variables/) , but somewhy use PUT http method. PUT method is for existing resource, that means, for existing variable, if you want to change its value, for example. To create a variable…

@Johannes F_ Knauf I suspect this also can be configured through this variable. This variable is flexible, its type is a string, so you can pass SSH_ARGS: '-e none -o HostKeyAlgorithms=...'. If you have some problems with this, give us the feedback and we will implement better solution taking into account your need.

@Rémi Mercier we have released a new version 1.1.0. Use pipe: atlassian/azure-web-apps-containers-deploy:1.1.0 variables: AZURE_APP_ID: $AZURE_APP_ID AZURE_PASSWORD: $AZURE_PASSWORD AZURE_TENANT_ID: $AZURE_TENANT_ID AZURE_RESOURCE_GROUP: 'your-group' AZURE_APP_NAME: 'your-app' DOCKER_CUSTOM_IMAGE_NAME: '...' ...…

@Jesse Schaaf this is done automatically by webhooks when you push bitbucket as pipeline workflow called `default`. If you want to run specific pipeline on specific branch you section `Branch workflows` in the doc https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/ Also read the section Keywords after…

@cgray i see one of possible root cause that you may set the owner while working with files or file that you will pass as RESOURCE_PATH variable. If that helps you, try executing such lines before running a pipe: chmod +rw $RESOURCE_PATH (adding -R option if resource path is a folder, not a single file). Looking forward to…

@Vitor Oliveira let's investigate more about that. Have you tried to run the pipeline after failure again. Does it still shows error on the second execution? The error show that stack does not exist, that means it was not created. Unfortunately, I see here, it is not shown in the log why it was not created, but you could…

@t1279k thanks for the question, Our pipe is based on bitbucket api. Bitbucket api have several methods to authenticate. For now, you can setup app password and give it least granular permissions that are needed to execute (running pipeline permission, access to repositories for example etc.). This is explained in the last…

@Wilber Marcel da Silva thanks for raising this, this help us to do our best to keep an eye on API changes (looks like it could be temporary server issue) and to not do breaking changes without notifying. Anyway, I'll report it. If the case rise again, give us this feedback please with possible logs you can share publicly.

@Kyle Godfrey regarding SAM CLI, you can use the Bitbucket Pipe in your pipeline. Check it out if it cover your needs https://bitbucket.org/atlassian/aws-sam-deploy/src/master/README.md . Regarding layers, please give us more details about what exact layers you mean? If you mean lambda layers, this depend on your AWS…

@Alejandro Torroella I suspect it includes your entire project because you're located not in auth directory before executing pipe, but in the root. So by default, serverless packages your entire project. Based on this I can propose you either change directory by cd-in to the right directory before pipe execution or do not…

As an option you also may look at the Git Large file storage doc and see if it is worth to use

@Wilber Marcel da Silva please, could you share the output when using curl for example? I've just managed to upload 24 MB file using ui and curl both.. Also, what file size do you have? Perhaps, there is anyway the limit we don't know about and should investigate. Please, share also the pipeline log of pipe's execution.…

@Trip thanks for the question! I think that the problem is not that deployment-instructions file do not exist, that note is put in another type error's subsection. But what you initially referred to is right: you have the subsection in Troubletshoot guide called Troubleshooting all lifecycle events skipped errors There you…

@Gonchik Tsymzhitov @Tom McLaughlin thanks for reporting it. This is a bug and right now in our priority to fix. Temporary workaround is put such lines before second execution of pipe : - BITBUCKET_PIPE_STORAGE_DIR=.... <the issued directory> - chmod +rw $BITBUCKET_PIPE_STORAGE_DIR Regards, Galyna

@Douglas Kolpien ok, we'll discuss within a team this change, I'll notify you once we have an update for you. Cheers, Galyna

@Klein-Hans Escuton is smpp-laravel is right pattern? --exclude accept a patten wildcard, that means, you use: --exclude=*.envi or --exclude=smpp-laravel/*.envi. Regards, Galyna

@Douglas Kolpien indeed, we hardcode the location in s3 bucket. Our flow right now: we upload to $APPLICATION_NAME folder. One workaround for you is that you can pass APPLICATION_NAME as beta, but that means that application created also will be beta. Tell us if that is ok for you, based on this we consider true S3…

@Jaisa Ram regarding the last question, why if failed - the user you use in s3 and cloudfront, do not have permissions to execute Cloudfront actions. To fix this, you have to change policy (any permissions attached, inline policy etc.) attached to this user or create another user specific for cloudfront. Could you also…

@hanskokx I have to mention, that if you need more build minutes and often run out of free build minutes, you could upgrade your plan :) Be aware , that the pricing paid for new plan is there in workspace settings and you can evaluate if this plan is worth for this current project you're working on. You can also check full…

@Johannes F_ Knauf in version 0.5.0 you can use SSH_ARGS variable while using alternative port and pass, e.g., SSH_ARGS: '-o HostKeyAlgorithms=...' Looking forward to seeing your feedback, thanks! Regards, Galyna

@hanskokx this error means that your firebase.json does not satisfy json format. Check it out, perhaps, there is something you forgot to put or extra character. If you want , you also can share it here in the question. You could make a mistake by forgetting , delimiter between list elements for example. Example of…

 @Shaun Dishman yes, because this is the way how pipeline parses the variables. We will update documentation

@Shaun Dishman could you try use the same version but adding extra quotes? So your variable could look like this: MESSAGE: '"[${CLIENT_NAME}/${BITBUCKET_DEPLOYMENT_ENVIRONMENT}]: ${MESSAGE} (${BITBUCKET_TRIGGERER_USERNAME})"' Thanks! Sorry for late response . It is the question how pipeline infra is parsing things. In bash…

@rogiervancann you could use LOCAL_PATH: "your-dir/." Regards, Galyna

@nasfarley88 we have updated aws-sam-cli. Please, share your pipeline, the part of aws-sam-deploy usage, and the template (you may put some sensitive things as hidden, but we need a template to understamd the exact case of failing and see the structure you're using). We will investigate your case separately and notify you.…

@Nikolai Zhukovyou can pass a directory that contains your .yml files for kubernetes to apply. Like RESOURCE_PATH: 'dir', where dir will contain 1.yaml , n.yaml Regards, Galyna

@aeris_alexnow you can use updated version, try, please 1.0.1 . Looking forward to see your feedback!

@Tarek Abdel Sateryou need to use aws cli for that, to update image tag. If you know some tags that you find your task definition by, use aws cli command describe-task-definition (by family, revision etc.) , describe it, clean up non-acceptable fields , change your image tags. The new task definition will be registered ,…

@Johannes F_ Knaufok, thanks, we'll notify you about the update.

@Shaun Dishmanyes, that is enough, thanks! I guess I can see the root cause - you're using `[` `]` characters, that are considered as structure. Looks like this is a bug, starting from 1.0.0 version. Temporary workaround for you, if you need the pipeline to succeed just right now : you can downgrade to previous versions.…