rancher-gitlab-deploy | Painless deployment of projects | Continuous Deployment library

by cdrx Python Version: 1.7 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | rancher-gitlab-deploy Summary

rancher-gitlab-deploy is a Python library typically used in Devops, Continuous Deployment, Jenkin, Docker applications. rancher-gitlab-deploy has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install rancher-gitlab-deploy' or download it from GitHub, PyPI.

rancher-gitlab-deploy is a tool for deploying containers built with GitLab CI onto your Rancher infrastructure. It fits neatly into the gitlab-ci.yml workflow and requires minimal configuration. It will upgrade existing services as part of your CI workflow. Both GitLab's built in Docker registry and external Docker registries are supported. rancher-gitlab-deploy will pick as much of its configuration up as possible from environment variables set by the GitLab CI runner. This tool is not suitable if your services are not already created in Rancher. It will upgrade existing services, but will not create new ones. If you need to create services you should use rancher-compose in your CI workflow, but that means storing any secret environment variables in your Git repo.

Support

Quality

Security

License

Reuse

Support

rancher-gitlab-deploy has a low active ecosystem.

It has 435 star(s) with 93 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 42 have been closed. On average issues are closed in 75 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rancher-gitlab-deploy is 1.7

Quality

rancher-gitlab-deploy has 0 bugs and 5 code smells.

Security

rancher-gitlab-deploy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rancher-gitlab-deploy code analysis shows 0 unresolved vulnerabilities.

There are 1 security hotspots that need review.

License

rancher-gitlab-deploy is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

rancher-gitlab-deploy releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

rancher-gitlab-deploy saves you 141 person hours of effort in developing the same functionality from scratch.

It has 354 lines of code, 5 functions and 3 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed rancher-gitlab-deploy and discovered the below as its top functions. This is intended to give you an instant insight into rancher-gitlab-deploy implemented functionality, and help decide if they suit your requirements.

This function is used to create an apis .
Turn HTTP requests logging .
Prints an error message .
Print a message .
Display a warning message .

Get all kandi verified functions for this library.

rancher-gitlab-deploy Key Features

No Key Features are available at this moment for rancher-gitlab-deploy.

rancher-gitlab-deploy Examples and Code Snippets

No Code Snippets are available at this moment for rancher-gitlab-deploy.

Community Discussions

Trending Discussions on rancher-gitlab-deploy

.NET Core embedded resources + Gitlab: ERROR: No files to upload

Upgrade Rancher 2 workload from CLI

Gitlab-CI Deployment stage and task fails with wrong Rancher API Url and Key

QUESTION

.NET Core embedded resources + Gitlab: ERROR: No files to upload

Asked 2020-Jan-21 at 07:08

I am working on the .NET Core solution below:

and I am using the Gitlab CI definition below:

.gitlab-ci.yml:

...

ANSWER

Answered 2020-Jan-21 at 07:08

I am not sure why this post has been down-voted, but fun fact, seems there is a bug in Rider 2019.3.1.

The issue arose because even though the file was showing up as GetOrderRelatedInfoForAccountingEntryCreation.sql in Rider aka pascal case it was actually written as a camel case (i.e. getOrderRelatedInfoForAccountingEntryCreation.sql) on the disk, go figure.

Once the name adjusted to pascal for the actual file on the disk, everything worked fine.

Source https://stackoverflow.com/questions/59800982

QUESTION

Upgrade Rancher 2 workload from CLI

Asked 2019-Mar-01 at 20:40

I have created a workload on Rancher. This workload created from an image which is hosted on a gitlab-ci project registry.

I want to force rancher to download a new version of this image and upgrade workload.

I want to do this from a .gitlab-ci.yml script. How to do this with Rancher version 2? With Rancher 1.6 I used this script:

...

ANSWER

Answered 2018-Jul-04 at 12:50

In rancher 2, much of the management of workloads is delegated to Kubernetes via its api or CLI (kubectl).

You could patch the deployment to specify a new image/version, but if you are using a tag like :latest which moves, you will need to force Kubernetes to redeploy the pods by changing something about the deployment spec.

One common way to do this is to change/add an environment variable, which forces a redeploy.

In Gitlab, set two variables in your gitlab project or group to pass authentication information into the build.

The kubectl patch will update or add an environment variable called FORCE_RESTART_AT on your deployment's container that will force a redeploy each time it is set because Gitlab's pipeline ID changes.

You will need to specify the namespace, the name of your deployment, the name of the container and the image. If the image tag is changing, there is no need to supply the environment variable. If you are using :latest, be sure that the your container's imagePullPolicy: Always is set, which is the default if Kubernetes detects an image using :latest.

The image diemscott/rancher-cli-k8s is a simple image derived from rancher/cli that also includes kubectl.

Source https://stackoverflow.com/questions/51139177

QUESTION

Gitlab-CI Deployment stage and task fails with wrong Rancher API Url and Key

Asked 2018-Jul-21 at 09:03

I have a Gitlab CI/CD setup that deploys a spring boot application to a DigitalOcean droplet using Rancher.

The task fails with a wrong Rancher API Url and Key error message when in fact, those API details are correct judging from the fact that I have run the deployment manually using the "rancher up" command from the rancher cli.

Screenshots

.gitlab-ci.yml source

...

ANSWER

Answered 2018-Jul-21 at 09:03

I eventually found the cause of the problem by doing a bit more research online. I discovered that the RANCHER_URL that was required was the base url rather than the full url provided in the Rancher UI. For example, I was initially using the full url generated by the Rancher UI system that looked like this http://XXX.XXX.XXX.XX:8080/v2-beta/projects/1a5. The correct URL is http://XXX.XXX.XXX.XX:8080/.

I set the RANCHER_URL as a secret environment variable in Gitlab Saas (Cloud/Online).

I appreciate everyone that tried to help.

Thank you very much.

Source https://stackoverflow.com/questions/51420216

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rancher-gitlab-deploy

I recommend you use the pre-built container:.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: