Igor Stoyanov Atlassian Team

@Toby Onono hi. Please, check this post. Regards, Igor

@Avinash Sachdewani hi. Thanks for your question. We will bump azure-cli in this pipe, and will notify you when new version become available. Regards, Igor

@Charlie Retzler hi. Thanks for your question. We will update pipe to the latest version and notify you. Regards, Igor

@Tommo hi. New pipe version released with fixes you suggested. Regards, Igor

Hi @Gazi Dizdaroğlu . New pipe version released with feature you requested: oidc: truescript: - pipe: atlassian/vault-secrets:0.5.0 variables: VAULT_ADDRESS: "<your vault address>" VAULT_OIDC_ROLE: "<your created role name with attached policies in vault>" VAULT_AUTH_PATH: "my-custom-jwt-path" SECRET_PATH: "secret/foo"…

Hi @Kevin Helfer . Thanks for feature request. We will investigate this and notify you when new version with this feature will be released. Regards, Igor

@Venkat P some info. If you had setup AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY, AWS_REGION as Repository variables, the pipe will automatically use them according to: https://bitbucket.org/atlassian/aws-ecr-push-image/src/12710693b00ae7438763a360359d5b41b3de0135/pipe.yml#lines-6 Regards, Igor

@Venkat P . I think this is not necessary: """ - pip3 install awscli - IMAGE="709724358365.dkr.ecr.ap-south-1.amazonaws.com/testrepo" - TAG=latest - aws configure set aws_access_key_id $AWS_ACCESS_KEY - aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY - aws configure set AWS_DEFAULT_REGION $AWS_REGION - eval…

@Jay Seletz hi. I also have a question. If pipeline fails, why it should not be in failed state on retry? Only example i could imagine is to wait for some infrastructure become available. And if pipeline could change state from FAIL to SUCCESS after some time, why don't add a condition in pipeline in repoB to run until…

@Tommo hi. Thanks for your investigation. We will fix this in a future releases and notify you. Regards, Igor

@Samuel Bloch hi. Also some useful link about escaping. Regards, Igor

@Venkat P Thanks for your question. Please, take a look at this answer. Regards, Igor

@Clément Niot hi. The issue fixed in 0.1.1 release. Regards, Igor

@Engine Irie hi. Check this article. Regards, Igor

@Saqib Ur Rehman hi. The error points you, that you dont have Azure subscription when trying to login. Answering your question, take a look at Azure pipes here. Maybe this azure-web-apps-deploy pipe is what are you looking for. Also, please, next time create a new question with your own issue instead. Regards, Igor.

Hi @Clément Niot . There is a bug we can confirm. We will fix this and notify you. Regards, Igor

@Javier Martín hi. New version released according to your pull request changes. Regards, Igor

@Kyle Godfrey Hi. Thanks for your question. Firebase-deploy pipe updated to use firebase-tools@12.* Check if this solve your issue. Regards, Igor

@Yohan Le Bricquer Hi. Thanks for your question. Try to run scp without pipe usage to understand the problem is with the pipe or with the scp command. Regards, Igor

Okay, now i understood what your want according to: plugin method is mounted at the /auth/jwt path in Vault. Since it is possible to enable auth methods at any location, please update your API calls accordingly. Currently, pipe does not support different path, but i will add this as a feature request, and notify you when…

Hi @Gazi Dizdaroğlu . Please, provide more details to your question. `vault auth enable jwt` is not a custom name, it is how you enable jwt. I can not find any other occurences. Also this example does not use jwt at all: script: - pipe: atlassian/vault-secrets:0.3.0 variables: VAULT_ADDRESS: "<your vault address>"…

@Christof Koegler _Gaims GmbH_ hi. We released new version of the renovate-scan:0.2.0 pipe, where renovate docker image was updated to renovate/renovate:36.24-full. With regards to the feature request: It is not about one specific version of renovate, but about the pipe being updated regularly to stay in sync with new…

@Jessica Zalzman hi. Please, check Set up Pipelines SSH keys on Linux guide. Regards, Igor

@Jessica Zalzman hi. Have you tried to connect via scp without pipe usage? Also take a look at this articles: host-key-verification-failed-when-i-use-scp , fix-host-key-verification-failed Regards, Igor

Hi @Brad Vrabete . The issue with LABELS fixed in aws-eks-kubectl-run:2.3.0 pipe . Regards, Igor

@mvalent23 hi. Check this article, maybe it can help you. Regards, Igor

@Garth Wood . Sorry for misunderstanding. I thought you have problems with a pipe usage, not with pipelines. Let's wait if someone from pipelines team will provide a response here. Regards, Igor

@Garth Wood . Let's summarize. Your initial issue: Failed to update the function <my function name>: The provided image is invalid. Your example: - pipe: atlassian/aws-ecr-push-image:2.0.0 variables: ... IMAGE_NAME: $IMAGE_NAME What i told you: IMAGE_NAME is not presented in list of variables that this pipe supports. What…

@Garth Wood . You provided in your example: - pipe: atlassian/aws-ecr-push-image:2.0.0 variables: ... IMAGE_NAME: $IMAGE_NAME but IMAGE_NAME is not presented in list of variables that this pipe supports.

@Garth Wood . I mentioned you the process above (with pushing to ECR), because i can't see that aws-lambda-deploy pipe supports local Docker images, only ECR URI. Regards, Igor