rancher-gitlab-deploy
rancher-gitlab-deploy copied to clipboard
cdrx
Painless deployment of projects built with GitLab CI onto your Rancher infrastructure
my rancher user private ssl ca,and add --no-ssl-verify,happened error also,key url token is right; $ upgrade --service $MODULE --new-image $HARBOR_URL/$HARBOR_STORAGE_NAME/$MODULE:$DOCKER_IMAGE_TAG --no-ssl-verify Error: Unable to connect to Rancher at demo.rancher.com -...
Hello, I have an infrastructure where I use rancher 2.5 will this plugin work with that version? I'm having a hard time integrating it. Could you help me?
- Trim env. variable names and values when using with `--variables`. - Trim secret names when using with `--secrets`. - Add support for trailing comma in `--variables` and `--secrets`.
**Actual behaviour:** When passing multiple variables alongside with the `--variables` [multiline configuration](https://docs.gitlab.com/ee/ci/yaml/script.html#split-long-commands) might be used: ```yaml deploy: stage: deploy image: cdrx/rancher-gitlab-deploy script: - > upgrade --variables " DB_HOST=db.example.com, DB_USER=foo, DB_PASSWORD=bar...
Rancher 2.0
With Rancher 2.0 not far away, its time to start thinking about supporting the new API version. I'm considering rewriting this tool in Go, to make it faster / smaller...
@cdrx What are you thoughts to creating an end point to remove containers from Rancher? My use case is I use this currently to add and push changes to review...
Not sure if this is possible or not, but it would be nice if this was able to update by tag. Instead of saying ``` upgrade --stack my-stack upgrade --stack...
I would like to be able to dynamically change the container's commands. Could be a "restart --container-new-command yarn build && Yarn tests" but for upgrade would be helpful. `upgrade --replace-Command...
We need to catch `requests.exceptions.*` and provide a better error message