Igor Stoyanov Atlassian Team

@Aysu Saglam hi. Here you have a command that generated via pipe workflow: lftp -u $FTP_USER,$FTP_PASSWORD -e 'set ftp:ssl-allow no; mirror -vvv --transfer-all -R /opt/atlassian/pipelines/agent/build/ /test/;quit' $FTP_IP Try to execute this command locally first to understand if all works as expected, maybe you will…

@Mike Stanley hi. Happy to know you solved this issue for yourself. There are possible 3 reasons where this could happen: * Check correct permissions for the app password * Ensure you correctly encode with base64 the app password (linux and mac have different shell commands), copy/paste to k8s manifest without trailed…

@Manoj Kinage AWS CLI and boto3 are not the same tools. Boto3 does not support `taskDefinitionArn` request parameter in register-task-definition Regards, Igor

@Manoj Kinage hi. This pipe based on boto3 1.26 version. According to docs there is no request parameter `taskDefinitionArn`. That's why your task-definition failed validation. Regards, Igor

@Sunil Lath hi. Thanks for your question. Maybe this article will help you. Regards, Igor

@Edoardo Pirovano hi. Since you already implemented this feature here, please follow the contribution docs to suggest this feature. Please, use Fork (check the docks). You are welcome and thanks for contribution. Regards, Igor

@Srinivas Nekkalapudi hi. You should not use dynamical variables inside your aupris-frontend yaml Kubernetes manifest file. And As @Oday Rafeh mentioned, you could create template instead, fill it with needed variables and create according manifest. Also, optionally, you could validate your generated manifest. Regards, Igor

@João Scaleão hi. Try to use one-liner in `EXTRA_ARGS`: EXTRA_ARGS: "--include="*.txt" --include="MyFile?.txt" Regards, Igor

@Bhavya Yamali hi. Could you confirm that bitbucket-pipelines.yml file presented in triggered repository? Regards, Igor

@Emmanuel Cohen-Laroque hi. Your pipe command was not resolved correctly. Please, take a look at the pipe README, you should provide apply related arguments under `KUBECTL_APPLY_ARGS`, but since `-f` is used by default, you could omit it. And `--force=true` argument should be passed to `KUBECTL_ARGS`. So your script should…

@Sam Ware hi. We added this feature as a task to our backlog, so the process when feature goes from tickets to our tasks passed. Now you should wait when this feature will become available if our team will find an option of how to implement this. Regards, Igor

@Sergei Artemov hi. Thanks for your suggestion. It's a complex case for waiting for a deployment on kubernetes services, so unfortunately this is not supported in the current implementation. If you’d like to suggest a pipe to be improved, please, find the appropriate ticket in the list of existing tickets , vote for them…

@Jason Redwood hi . Thanks for your question. This pipe based on aws s3 sync where DELETE_FLAG is option: `<span>--delete</span> (boolean) Files that exist in the destination but not in the source are deleted during sync`. To test your case you could try directly call `aws s3 sync` command inside pipelines script, and…

@David Bronke You could try the next approach: * install aws-cli in the step * aws authenticate docker to an Amazon ECR * docker pull the image from ecr Additional links: Pulling an image , Private registry authentication To install aws-cli: script: - curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64-2.2.9.zip" -o…

@oobug hi. Thank you for investigating this bug. We will notify you when new pipe version with fix will become available. Regards, Igor

@lgLindstrom hi. Thanks for your question. Please, check this answer. Regards, Igor

@David Bronke hi. Thanks for your question. Try Use AWS ECR images in Pipelines with OpenID Connect guide, maybe it is your case. Regards, Igor

@W seems like you used short-living token, that expired in 1 hour. For long living tokens you should set up service account via this guide: https://cloud.google.com/artifact-registry/docs/nodejs/authentication#auth-password Regards, Igor

@W hi. Thanks for your question. have you tried these examples from the README: Publishes a package from the package1 directory to a private registry. Support authentication url environment variable in case of npm registry url host cannot be used for authentication. script: - pipe: atlassian/npm-publish:0.3.2 variables:…

@Neethu Philip hi. Thanks for your question. Currently, this is not supported in the pipe. We will investigate this and notify you if this feature will become available. Regards, Igor

@Mike Beaton hi. Maybe you could try to use Atlassian ftp-deploy pipe: script: - pipe: atlassian/ftp-deploy:0.4.0 variables: USER: my-ftp-user PASSWORD: $FTP_PASSWORD SERVER: 127.0.0.1 REMOTE_PATH: /tmp/my-remote-directory Regards, Igor

@Aaron Durant Great! You could mark your answer as Accepted, so the other users could see that your case has solution. Regards, Igor

@Aaron Durant i think you should dive into this: https://github.com/aws/aws-cdk/issues/20935, especially: the CDK CLI does not have the capability to automatically pick the correct profile for the configured stack environment. The CLI needs some set of credentials to start with, and if you do not provide the --profile then…

Sorry, i read Development instead of Deployment.

@Aaron Durant hi. Please check the same for `staging` branch, where you investigated the error. Regards, Igor

@Aaron Durant variables defined in pipeline/deployment variables should be available without export. You could test this case with `echo <any unsecured variable>` command. Check the page for bitbucket variables and secrets Regards, Igor

@Joao Clemente hi. Our team released a new version 1.8.0 of aws-lambda-deploy pipe. According to README, now: This pipe checks for lambda to be in Active or Inactive State and LastUpdateStatus not equal InProgress before start executing. Regards, Igor

@Aaron Durant hi.This pipe requires the standard permissions: check them is this guide. Regards, Igor

@Aaron Durant hi. Check this guide. - step: oidc: true script: - export AWS_REGION=us-west-2 - export AWS_ROLE_ARN=arn:aws:iam::XXXXXXXXXXXX:role/oidc-demo - export AWS_WEB_IDENTITY_TOKEN_FILE=$(pwd)/web-identity-token - echo $BITBUCKET_STEP_OIDC_TOKEN > $(pwd)/web-identity-token - aws s3 cp s3://bucket/XXXXXX ./XXXXXXX…

@Nozim Khodjaev hi. Try to install requirements in the same step where you run you script: - step: name: Test script: - pip install -r requirements.txt - python main.py Also check that the last supported python version is 3.7 Regards, Igor.