Halyna Berezovska Atlassian Team

@Ferdi we have released new version with bumped aws-sam-cli to 0.53.0. Welcome to check it out Best regards, Galyna

@Tanvir Pathan , please provide us with your pipe usage in the pipeline. Check you don't have mistypo in repo name, commit etc. Looks like resource (perhaps the repo that is attempted to be accessed for the report , cannot be found)

also you can refer to examples, azure is recommending to use https://docs.microsoft.com/en-us/cli/azure/storage/container?view=azure-cli-latest#az-storage-container-generate-sas-examples , but I think still attention to spaces , \t, \n etc. should be paid

@Thomas Beauvais try, please, the next command for generating the token az storage container generate-sas --name <container_name> --account-name <storage_account_name> --expiry ${SAS_TOKEN_EXPIRY} --permissions ${PERMISSIONS} | sed 's/["\t]//g where PERMISSIONS is 'rw', for example or other permissions you would l like to…

Also, every pipe's repo has a documentation, please refer here . Regards, Galyna

@Milad Rezazadeh please, provide us with pipe usage example in the pipeline. I just tried it and it downloads the image in the pipeline. <span> Pull complete</span><span>Digest: sha256:***</span><span>Status: Downloaded newer image for bitbucketpipelines/serverless-deploy:0.1.6</span><span>INFO: Deploying your serverless…

@ILI.DIGITAL AG please, provide us also logs, cause there can be many root causes tied to file issues

@Thomas Beauvais it seems like it is azure issue, because our pipe only copies and if the token is not validated by azure, it is either token or azure problem. Our tokens generated are working properly. However, haven't you tried to generate sas token via azure portal?

@Bruce Wilcox according to google docs https://cloud.google.com/iam/docs/understanding-roles?hl=en#app-engine-roles you could try to remove first role and deploy. It is said there that deployer has enough permissions to deploy, and this is a subset of app engine admin role, while admin can also modify access to application…

@Steven Lindelauff right now we are not really to support this. The reason is that we recommend users to use sftp instead of ftps since ftps looks like a bit legacy. You can find pros and cons here https://www.nsoftware.com/kb/articles/legacy/sbb/ftps-vs-sftp.rst . We actually recommend to adapt your pipeline to use…

@fam513 ok, thanks for reporting. Right now I think it should basically support all update_stack options , but we'll discuss it within a team. Regards, Galyna

@Jared Bates yes, I see minor issue : sam deploy inherits cloudformation where stack name is required, but if sam does only package, it actually does not use this variable. I see this as a minor issue that you have to specify STACK_NAME variable but it will be never used. Thanks for reporting, Galyna

@Dmytro420 I suppose you can do chmod for build directory before you share this artifact to the next step, just after npm run build, firebase should allow this. If not , play with permissions in predeploy script.

@fam513 ok, we will investigate this. But tell your exact case and share logs please and at what exactly pipe parameters you have for cloudformation, because right now I see it should be supported and if not, this can be actually a bug. Anyway, thanks for reporting the case. Best regards, Galyna

@Sarath could you provide more information on how you configured a pipe execution and failing logs? Regards, Galyna

@devevasoftwaresolutions first thing that I see the problem will be (now or later) is: <span>You</span> <span>do</span><span> not appear to have access to project </span><span>[</span><span>evadev0010</span><span>]</span><span> or it does not exist</span> The key_file that you are using may be inappropriate for this…

As a workaround for now I can see you could put tag right to the definition like you do and before you can remember this tag as a variable if it is possible. Or you could parse definition json file with jq and get the tag.

Also look at the version of node, it may matter. In atlassian default image we have node 8.9.4 and if another version of node fiex that, you can use the image you want with appropriate version of node I see some bug https://github.com/grpc/grpc-node/issues/1086 where workaround was downgrading node. The same may happen…

@brianbriscoe no, we did not see others with this issue. Sorry, I did not tied your initial failing script to the problem, so I think since the npm is failing to execute in pipeline it is worth asking bitbucket-pipeline team, for this you can create new question with `bitbucket-pipelines` tag or add this tag to the current…

@Ashwani Kumar yes, I see... Looks like this is a bug or not supported feature. Thanks for reporting, I will let you know once that is enrolled fully

@brianbriscoe I suppose, the error can be that your AWS service did not update yet the environment with appropriate version and not much time has passed since update environment command was executed. It can happen if AWS is updating your environment not very fast (for instance, big or performance-consuming deployments) and…

@David Keaveny yes, this is because you are trying to find files in no-root directories. In python glob that we use there is such specific to search recursively: script: - pipe: atlassian/git-secrets-scan:0.4.3 variables: FILES: "**/*.txt **/*.json" This is not obvious, see how it should work in our doc: Git Secrets Scan,…

@Ashwani Kumar Yes, you are right, it is not explicitly supported. https://bitbucket.org/atlassian/aws-ecs-deploy/src/dd7bab5f57211073f36a28d268155fb0f0c02ab9/pipe/main.py#lines-117 https://bitbucket.org/atlassian/aws-ecs-deploy/src/dd7bab5f57211073f36a28d268155fb0f0c02ab9/test/test.py#lines-185 Actually, you can try to…

@brianbriscoe the reason may be the application was not deployed successfully on your environment or sth else. Can you provide us with full log of aws elasticbeanstalk Pipe execution, so that we can investigate the root cause? Regards, Galyna

@brianbriscoe I see you are using bitbucket-pipelines. Did not you try to use our AWS Elasticbeanstalk Deploy pipe in your pipelines? If this is issue with the pipe, please clarify what version you are using, specify the pipeline step, where you are using this pipe and we will figure out the failure. But if it is issue…

@David Keaveny hello, we released new version of git-secrets-scan 0.4.3, there is a fix of wildcard issue, indeed , subprocess tool did not work with wildcard *. Now it should work in 0.4.3 and your example FILES: '*.cs;*.json' also will work, but you need specify this variable like this: FILES: '*.cs *.json' without…

@chris_todhunter please clarify, what error you have? I am able to download an image and it is not dumped from dockerhub. Also, did you try newer versions? Regards, Galyna

@[deleted] It happens, glad if I could help you. If you want , you can also made your pipe officially available for others (via our pipes page https://bitbucket.org/product/features/pipelines/integrations ) as it is written in the doc! We are happy to new contributors :)

@John C I have some questions to define the root cause: * did it work previously with the same version? * what exactly steps did you add since the time it worked? Could the be the reason of failure? Are you doing something specific with BITBUCKET_PIPE_SHARED_STORAGE_DIR directory in those added steps? * You can add to your…

@[deleted] docker://your_account/repo:tag should also work. But let's define the root cause. I see the version 1.0 , but it does not comply Step 10 in the doc or is it just an example? Anyway check the git tag with the version, that you write in pipeline, exists in your repo. If you made repo public , could you share it…