Halyna Berezovska Atlassian Team

@Johannes F_ Knaufwe've discussed your case. So we think that it would be nice improvement. Tell us if you want to contribute yourself or we can do it in the future release. Regards, Galyna

@Dan Clausen @Ørjan Solli I need to correct that executing pipes, you need to put triple escaping: DESTINATION: 'https://myaccount.blob.core.windows.net/\\\$web/' The same resolved question is here https://jira.atlassian.com/browse/BCLOUD-20350 We will also update the docs accordingly. Thanks for raising the question…

@Johannes F_ Knaufwe try to not hardcode such stuff in the pipe. But in the tests it can be implemented. About repository ssh keys: we are not using them in this pipe's tests. We are authenticating using test environment variables. Don't worry, if it does not work for you, we will contact in the pr or by email. Just tell…

@Shaun Dishmanthanks for raising this question! Could you please, share the pipeline of how you're using the pipe? It is important for us to see how you pass variables to the pipe. I see root cause can be there. Regards, Galyna

@DaeruinI guess, this is due to local cache. If you really need to update VERSION_NUM var in the exact same step - I think, you can parse the response of PUT call. Or explain us your use case, and we can help constructing well-written pipeline. Regards, Galyna

@Clayo84no matter, formatting is fine! I see you're using ${BITBUCKET_REPO_SLUG}-cloudformation-${BITBUCKET_BRANCH} as STACK_NAME variable. Are you sure that your branch was not changed there ? Me, did not change the branch while testing and it worked. Also, just in case I tried to test another case and switch to the new…

@aeris_alextry as a workaround for now LOCAL_PATH: '.' I guess, for current directory it is working differently. We will investigate more and update documentation appropriately . Also, I think this is a bug. We'll notify you about the fix and doc update also. Thanks! Regards, Galyna

@Clayo84we are trying to reproduce your issue and find root cause now. Could you share your bitbucket pipeline file, that part where you execute cloudformation pipes, both versions? I just tried to reproduce and did not succeed, hope after your sharing will get the root cause. Regards, Galyna

@Johannes F_ Knaufthank you for raising this, we will consider this for the future updates and bugfixes. Also, we are always happy to meet contributors to our pipes. Contributing, don't forget about tests and semversioner change and other stuff , referring to documentation for contribution…

@Ashish Awasthifirstly, you need to create your lambda or update the lambda with environment variable. The only way I know - it can be done via sam template. You can do this with sam deploy pipe. See example how to do this with sam deploy…

@Ranjit Sharma yeap, now I can see this. You can submit a bugfix request to open bitbucket pipelines jira or try to find suitable request here . I know what it can be - perhaps when your variable match with some pattern in logs, it can be substituted. I saw it a couple of times. For new request please, put exact steps to…

You also may want to play with service definitions. Look how to define own service with variables here https://support.atlassian.com/bitbucket-cloud/docs/databases-and-service-containers/#Define-a-service

@Nagore García Basically, you may want to build and push to some registry image firstly. In this case you can use it as in this documentation https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments/ or as a service - for service definition have a look at…

@[deleted] @David Corto I guess, you can try if the next feature will be implemented https://jira.atlassian.com/browse/BCLOUD-13014 (you would add role arn variable for assuming, for example). I linked this, because you can vote for this feature . Or if this does not suit, create a new suggestion request and we will gather…

@Anshul Shahif agter such text there are indeed no logs, it can be that something wrong with the script dwh_iam_role="$(aws cloudformation describe-stacks --stack-name ${PROJECT_SHORT_NAME}-${ENVIRONMENT}-infra --profile ${BITBUCKET_BRANCH} | grep -A1 OutputKey | grep -A1 DWHCopyExecutionRoleArn | grep OutputValue | tr -d…

@Ranjit Sharma thanks for the question. Please, specify what unknown variables do you mean that are mixing up? In pipelines infra when running a pipe, it is logged how the container is run. It may help to discover the problem and to see quickly what global variables are passed. Also, you can see the trace of your pipe…

@Daeruinwhen you have updated the value - you will have value changed either in PUT response or in response of NEW get request to the variables. This is the question of bash script you're using - you re not overriding $VERSION_NUM variable in local script section. So you have to update it somehow. BUT be awarte that if…

@Nagore Garcíayes, sure, you can do it, just ensure you put building-pushing container step before actions where you use this image

@bruno @Nana Insaidoo thanks for contacting us. We have discussed the case in the team - I informed agreement page is kind of broken. You still should be able to contribute , just make pr, as you always did, and we will accept that. Also I'll inform when the agreement page is fixed. However, it should not block your PRs.…

@Nana Insaidoo You did right, Atlassian community or bitbucket pipelines channels are ways to communicate. Right now we support trusted vendors to contribute. It means that if the pipe is, for example, deploying to Sonarcloud or Meterian etc., you have to work at Sonarcloud or Meterian company correspondingly, not just be…

@Ralph BolligerI managed to reproduce your problem and fix it. So, try not build/* , but build/ in the variable LOCAL_PATH , with same EXTRA_ARGS. The thing is build/* gives you all not hidden files Regards, Galyna

@Ralph Bolligeryes, sure , the logmay always be helpful. I will try to reproduce this again. Perhaps, I have missed something. For example, I have just noticed, you use unusual name of remote dir `--stripped--`.

@Evan Rosalok, I got it. The thing is that bitbucket pipelines execute bash script. So you can find a way to do this right now through bash ignoring way. For example make test || true. Like this you can ignore the failure in bash, but still you will have test reports file I think. Also, you may consider test report…

@Evan Rosalso in your case you could put tests results to different files in after scripts and then in the separate step you consolidate those results

It is actually very important for such situation to sync from master, otherwise you may have issues in your branch every time. If you sync, the task gets simpler both for branching and deployment

@ktomkthanks for your comment. I think , we have similar pipe doing rsync operations - rsync-deploy. So if it is fine, @zzzro , you may try that https://bitbucket.org/atlassian/rsync-deploy/src/master/ . Thanks for your case you explained in detail. I guess I understood this. I have some comment: when you push some changes…

@shailab I see that --namespace and timeout are common args for kubectl, not for the status. You can move them to the beginning of the KUBECTL_ARGS Regards, Galyna

@Diogo Borgeswe support things that are available in the image you use. If you use atlassian default-image 2, there will be bash and sh. You can use also mcr.microsoft.com/powershell image - there is pwsh , bash, sh. Look at the screenshot attached, I've just tried that pwsh shell is also available, just like sh. You can…

@Drew Heasmanglad that you figured that out. If we support this in the pipe, would it be more handy for you instead of using the script? We think that this case is quite often

@zzzrothanks for using the pipe. Looks like --file-exists-behviour OVERWRITE does not do actually what you want. It does not compare what files have changed: First option In aws docs I see that this param can be described as the following: OVERWRITE: The version of the file from the application revision currently being…