Halyna Berezovska Atlassian Team

Great news!

@Kostya Kostyushko I meant somethong like script: - kubectl ... > output.yml - pipe: atlassian/kubectl-run:2.0.0 variables: ... RESOURCE_PATH: 'output.yaml' The location of your resource file can vary depending on your requirements and project structure. Regards, Galyna

@Drew Heasman @Francis Poulin check out the new pipe's version (example below). Looking forward to seeing your feedback! script: - pipe: atlassian/aws-lambda-deploy:0.8.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION FUNCTION_NAME:…

@Robert Wen_Cprime_ yes, you can try going with almost same code, they only difference will be that EXTRA_ARGS will be a string , since in rsync-deploy is written in bash, not in python. And since rsync is different utility, you will use sth like , EXTRA_ARGS: "-e 'ssh -o $PROXY_COMMAND' ", where…

@Kostya Kostyushko you could execute create configmap firstly and save it to file, and then run a pipe with RESOURCE_PATH equal to that file you saved output to Regards, Galyna

<span><a href="https://community.atlassian.com/forums/user/viewprofilepage/user-id/3810057">@Srikanth Mamidala</a> </span> <span>I wonder if you still use our pipe or created a fork? I see you downloaded newest version of our kubectl-run.</span> <span>it says </span> `<span>error loading config file…

@Drew Heasman @Francis Poulin welcome to try our new version (0.8.0) with new variable PUBLISH_FLAG: '--no-publish'. Hope you' ll find this useful. Contect us in the case of more questions. Regards, Galyna

@Srikanth Mamidala now it seems it will be another error. Could you share your Dockerfile as text, so I can test it as pure docker image? BTW, whatever flow you choose to deploy, e.g. ServiceAccount, Role/RoleBinding , that you were proposed, you can form it in the pipe also, it will make your pipeline look much cleaner. I…

@Srikanth Mamidala we are refactoring our pipes to use absolute paths, actually, this is a good practice. But anyway I've just built both versions with absolute paths and not , and it is working. I can say more if you could share your Dockerfile. Also, the question: have you followed the structure that kubectl-run initial…

@Eduardo de Vila yes, for sure, you just execute bash code, just like you installed heroku cli locally to linux (follow https://devcenter.heroku.com/articles/heroku-cli#other-installation-methods) and follow also heroku doc depending on what you exactly need https://devcenter.heroku.com/articles/heroku-cli#getting-started.…

@Thomas Schmitt yeap, we actually recommend to use rsync more, since it is more optimized and copies files faster,, when there are many . However, We will reproduce this in scp deploy

@Vlad Kalinin @[deleted] @Shirish_Veerabattini @Akhilesh singh Pilkhwal we developed this pipe to support samconfig.toml config, where you can write your requirements according to the doc https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-config.html: version=0.1…

@[deleted] I also should provide such details that we have bash-4.4# ldd --version musl libc (x86_64) Version 1.1.20 1.1.20 version installed. But I don't think that it should affect the working pipe. We will try to reproduce this in the meantime

@mounika.nallagundla we don't try it with repository id and workspace id, but with workspace name and repository name. I also tried with workspace uuid and repository uuid, it also works. SO there could be two issues in your request: - something is wrong with authorization scope. perhaps you did not give required right for…

@[deleted] we will try to reproduce this and fix soon. However, we need some details for you. Before did you manage to use older versions without fail? The thing is we did not change any version and did not met such a problem before. Regards, Galyna

@BenHarris90 we think that it would be nice improvement for our pipe, thanks for raising this. We are happy to follow AWS new features and will notify you once we release it in the next update. Regards, Galyna

@Luiz Rocha thanks for raising the issue. If you have some related logs, please share that, it will help to discover root cause. Cheers, Galyna

@Srikanth Mamidala I explained the request there since it is quite common.

@mounika.nallagundla for example, you can create a custom pipeline that is posting a schedule. But it actually can be done only once, if you're not gonna to remove it. But anyway, to automate this more, in bitbucket-pipelines.yml you can write something like this: schedule-pipeline: &schedule-pipeline step: name: Schedule…

@Srikanth Mamidala we discussed in a team your case. A nice approach to support this is to allow to mount additional dependencies binaries to docker container (for example, you could install oci cli and mount to docker container oci binary. You could vote for such ticket in Bitbucket Pipeline Jira…

@Alberto García Olivero npm-publish allows to publish to custom registry also. Follow `Advanced example 2` section to accomplish your goal https://bitbucket.org/atlassian/npm-publish/src/master/README.md . Don't forget to put NPM_AUTH_REGISTRY_URL, since this often is different from npm registry url, where you upload…

@mounika.nallagundla Pipelines UI contains wide-used propositions for period. For custom schedule you can post this schedule using bitbucket api (doc https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines_config/schedules/#post ). Regards, Galyna

@Srikanth Mamidala I hope certificate is not real. We will invedtigate this and discuss within a team. Thanks

@stefanoc this means , that when you install dependencies, they failed to install. The possible reason is that you freeze version, and some package, for example, pandas, require numpy of another version, BUT you have a conflict here. Try to install it locally and ensure you have latest pip package manager, they recently…

@Srikanth Mamidala looks like kubectl CLI itself does not recognize your cluster, because this error comes from kubectl apply command result and we just log it in the pipe. If you could share example (non-live, with non-existing names, but similar to what you have) of your config file to be applied in k8s, that one where…

@Joshua von Damm cache feature is embedded, but it works automatically, so it is supposed , that you should not cd to it or ls manually. Anyway, caches are lying in the appropariate directory where appropriate app, like docker, would create a cache. Look at the doc, table in the section Pre-defined caches…

@Johannes F_ Knauf ok, thanks for such recommendation, we'll discuss it within a team

@avikuma please, share more details, which Bitbucket AWS Pipe you're using (we don't have there such feature, as I remember) We can have this ability in many pipes that involve s3 buckets, so we need more details about your case. Regards, Galyna

@Thomas Schmitt dist/* is not counting hidden files in bash. You can use LOCAL_PATH: 'dist/' to take into account hidden files. Or if that does create a redundant folder for you, you can actually cd to your dist before using the pipe and use not dist, but '.' or './' as LOCAL_PATH there Looking forward to see your feedback…

@ili have you tested this locally? If the file is empty it depends on .NET cli . I see the separate option for test results folder in dotnet test command * -r|--results-directory <RESULTS_DIR> The directory where the test results are going to be placed. If the specified directory doesn't exist, it's created. The default is…