fix references after moving to baloise orga

Author: christiansiegel

.travis.yml

@@ -9,7 +9,7 @@ env:
     - secure: "cyp11ZUB/GJ3o96oFZvMEZPW0rPzWnOHXcQTgQcQBz328+OUBgg/rY61BwRAjk57Kqjr9w7FWCJCjvzHLiTk/wVwsKo3pQw9nJPiyblFKAtGunJfA/rrwVqaDTvki9zWtQKqwteQ9gPpVG4RAsCVVYp0nCsCCfmBsw6iWnHSiQKwpw2g23PTG97xkioFcMNdetdt1+fqQC23fcEd7aktPlq0wRilSOZQRk87zF9tiRzTIL9Cl81guh0xC5FY4KG6egS82DAv0gANQO/aJr2vWpTZRPukL5GkFUpFfRFcH9nszz39R8OQ5B+SWJxbWSkbIN0k5IQyZyN7rWqQkk1p84JSMn3O4/0RSrAXDp93dcb1OxAYQq0o+upBZfcpKBFAAXy0xIHKu8uQe2BohREB2EVlfQIO1iXYnB2hUo7hUyHFQ2btjT1Qq8GdU1uudKmaueDC51WlHmcvBgAptQXD4ESagiL5vSCfw4S7gUevdrxrV+GLkUYGxqzd20CA0kWf05KBYX3JHh02sTwQm+x8cQWL4aHQ/vQN+zYRLh+TrgoOKoR50L5xK1Eyq3boTZ0R6wOcvKgA9ViWZ2ZDckB2FlM2Vpk4Zvmg5cBlgTwP96aQXh06TZgfvx26Ni9JaWb59iZSVSl1RWdeeIv5VZqLBX2MR5jy2rlccg8ws5DqWAQ="
     # GITHUB_TOKEN
     - secure: "MGMSLhzZuFGVbCGR+EcyC0SODyccmJlKG9vjbSUl9Lxs7Hxm1C9vpcn6eP5LhZtsX3Qsarc52TzM93bwWJWS3Wc1nzNzB/p32MtvD3lECAMps8592PAhmYhNl0Dn2WauNlD/kCDtYO42IZ5jRu74jnOvbqvqJDUasposPGx7MIC2NxFHHEZzuPf4TVf7lpjWYcI08yNTBLqeykAZqdYMXH+tzuHp2DagyP4Ay6LxnqfTdYD980FbWf1ObgfpXAMpzhFC0RP18J5MURF/lKaX/9kal9NGex51UHaFZXiyVNqIMF1Wkw1jRoN95duKGI1F5onnx8bqFoHA/4g5PqUXHBDZfZPq0kZxj3qBCttxOY+M5b0VRm8fAAO2Jh/ly8newk1KElV3Uxy7YHhnEY4OEWQLq2nbHYCFH2qVHXuJovzqn1/3waAdDKpg0SkaW9N9Kud+SZtKkXk5NE97Rt8S+4v2hD+9vZvus33FPBFzZgNN7iRLFAAqMTVnauYVoiQos2XsuEyol2swJeMjZYhUM9m3N05K65uAfj3TWdHMAMw5LQrS8pWnKkQ/xhGEyx3vLih8P14YSeFDIFDD69SKX5pBUmQ1TAReaK8atElUTPcOKzHrGjNggVBxlPdK9bDLIE2CWOaIqYm+m9LbytfjllZT4FzFCBAchE4eShaBLYM="
-    - IMAGE_NAME=baloiseincubator/gitopscli
+    - IMAGE_NAME=baloise/gitopscli
 
 jobs:
   include:

CONTRIBUTING.md

@@ -12,19 +12,19 @@ Below are a few guidelines we would like you to follow.
 If you need help, please reach out to us by opening an issue.
 
 ## Report a bug 
-Reporting bugs is one of the best ways to contribute. Before creating a bug report, please check that an [issue](https://github.com/baloise-incubator/gitopscli/issues) reporting the same problem does not already exist. If there is such an issue, you may add your information as a comment.
+Reporting bugs is one of the best ways to contribute. Before creating a bug report, please check that an [issue](https://github.com/baloise/gitopscli/issues) reporting the same problem does not already exist. If there is such an issue, you may add your information as a comment.
 
 To report a new bug you should open an issue that summarizes the bug and set the label to ![bug](https://img.shields.io/badge/-bug-d73a4a).
 
 If you want to provide a fix along with your bug report: That is great! In this case please send us a pull request as described in section [Contribute code](#contribute-code).
 
 ## Suggest a feature
-To request a new feature you should open an [issue](https://github.com/baloise-incubator/gitopscli/issues/new) and summarize the desired functionality and its use case. Set the issue label to ![enhancement](https://img.shields.io/badge/-enhancement-52d13e).  
+To request a new feature you should open an [issue](https://github.com/baloise/gitopscli/issues/new) and summarize the desired functionality and its use case. Set the issue label to ![enhancement](https://img.shields.io/badge/-enhancement-52d13e).  
 
 ## Contribute code
 This is an outline of what the workflow for code contributions looks like
 
-- Check the list of open [issues](https://github.com/baloise-incubator/gitopscli/issues). Either assign an existing issue to yourself, or 
+- Check the list of open [issues](https://github.com/baloise/gitopscli/issues). Either assign an existing issue to yourself, or 
 create a new one that you would like work on and discuss your ideas and use cases. 
 
 It is always best to discuss your plans beforehand, to ensure that your contribution is in line with our goals.
@@ -39,7 +39,7 @@ It is always best to discuss your plans beforehand, to ensure that your contribu
 - As you push your changes, update the pull request with new information and tasks as you complete them
 - Project maintainers might comment on your work as you progress
 - When you are done, remove the ![work in progress](https://img.shields.io/badge/-work%20in%20progress-fc9979) label and ping the maintainers for a review
-- Your pull request must receive a :thumbsup: from two [MAINTAINERS](https://github.com/baloise-incubator/gitopscli/blob/master/docs/CODEOWNERS)
+- Your pull request must receive a :thumbsup: from two [MAINTAINERS](https://github.com/baloise/gitopscli/blob/master/docs/CODEOWNERS)
 
 Thanks for your contributions!
 

README.md

@@ -1,8 +1,8 @@
 
-[![Build Status](https://travis-ci.org/baloise-incubator/gitopscli.svg?branch=master)](https://travis-ci.org/baloise-incubator/gitopscli) 
-[![Latest Release](https://img.shields.io/github/v/tag/baloise-incubator/gitopscli)](https://hub.docker.com/repository/docker/baloiseincubator/gitopscli/tags?page=1)
+[![Build Status](https://travis-ci.org/baloise/gitopscli.svg?branch=master)](https://travis-ci.org/baloise/gitopscli) 
+[![Latest Release](https://img.shields.io/github/v/tag/baloise/gitopscli)](https://hub.docker.com/repository/docker/baloise/gitopscli/tags?page=1)
 [![Python: 3.7](https://img.shields.io/badge/python-3.7-blue.svg)](https://www.python.org/downloads/release/python-370/) 
-[![Gitpod Ready-to-Code](https://img.shields.io/badge/Gitpod-Ready--to--Code-blue?logo=gitpod)](https://gitpod.io/#https://github.com/baloise-incubator/gitopscli) 
+[![Gitpod Ready-to-Code](https://img.shields.io/badge/Gitpod-Ready--to--Code-blue?logo=gitpod)](https://gitpod.io/#https://github.com/baloise/gitopscli) 
 [![License: Apache License Version 2.0](https://img.shields.io/badge/license-Apache%20License%20Version%202.0-lightgrey.svg)](https://choosealicense.com/licenses/apache-2.0/) 
 
 # GitOps CLI ![Stability: Experimental](https://img.shields.io/badge/stability-experimental-orange)
@@ -14,11 +14,11 @@ GitOps CLI is a command line interface (CLI) to perform operations on GitOps man
 ## Quick Start
 The official GitOps CLI Docker image comes with all dependencies pre-installed and ready-to-use. Pull it with:
 ```bash
-docker pull baloiseincubator/gitopscli
+docker pull baloise/gitopscli
 ```
 Start the CLI and the print the help page with:
 ```bash
-docker run --rm -it baloiseincubator/gitopscli --help
+docker run --rm -it baloise/gitopscli --help
 ```
 
 ## Features
@@ -27,7 +27,7 @@ docker run --rm -it baloiseincubator/gitopscli --help
 - Create and delete preview environments in the config repository for a pull request in an app repository.
 - Update root config repository with all apps from child config repositories.
 
-For detailed installation and usage instructions, visit [https://baloise-incubator.github.io/gitopscli/](https://baloise-incubator.github.io/gitopscli/).
+For detailed installation and usage instructions, visit [https://baloise.github.io/gitopscli/](https://baloise.github.io/gitopscli/).
 
 ## Git Provider Support
 Currently, we support both BitBucket Server and GitHub.

docs/commands/deploy.md

@@ -3,7 +3,7 @@
 The `deploy` command can be used to deploy applications by updating the image tags in the YAML files of a config repository. Of course, you can also use it to update any YAML values in a git repository. However, only _one_ YAML can be changed at a time.
 
 ## Example
-Let's assume you have a repository `deployment/incubator-non-prod` which contains your deployment configuration in the form of YAML files (e.g. [Helm](https://helm.sh/) charts). To deploy a new version of your application you need to update some values in `example/values.yaml`.
+Let's assume you have a repository `deployment/myapp-non-prod` which contains your deployment configuration in the form of YAML files (e.g. [Helm](https://helm.sh/) charts). To deploy a new version of your application you need to update some values in `example/values.yaml`.
 
 ```yaml
 # Example Helm values.yaml
@@ -25,7 +25,7 @@ gitopscli deploy \
   --git-user "GitOps CLI" \
   --git-email "gitopscli@baloise.dev" \
   --organisation "deployment" \
-  --repository-name "incubator-non-prod" \
+  --repository-name "myapp-non-prod" \
   --file "example/values.yaml" \
   --values "{frontend.tag: 1.1.0, backend.tag: 1.1.0}"
 ```
@@ -73,7 +73,7 @@ gitopscli deploy \
   --git-user "GitOps CLI" \
   --git-email "gitopscli@baloise.dev" \
   --organisation "deployment" \
-  --repository-name "incubator-non-prod" \
+  --repository-name "myapp-non-prod" \
   --file "example/values.yaml" \
   --values "{frontend.tag: 1.1.0, backend.tag: 1.1.0}" \
   --create-pr \

docs/setup.md

@@ -6,18 +6,18 @@ Currently there are two different ways to setup and use the GitOps CLI.
 
 The official GitOps CLI Docker image comes with all dependencies pre-installed and ready-to-use. Pull it with:
 ```bash
-docker pull baloiseincubator/gitopscli
+docker pull baloise/gitopscli
 ```
 Start the CLI and the print the help page with:
 ```bash
-docker run --rm -it baloiseincubator/gitopscli --help
+docker run --rm -it baloise/gitopscli --help
 ```
 
 ## From Source
 
 Clone the repository and install the GitOps CLI on your machine:
 ```bash
-git clone https://github.com/baloise-incubator/gitopscli.git
+git clone https://github.com/baloise/gitopscli.git
 pip3 install gitopscli/
 ```
 You can now use it from the command line:

gitopscli/commands/create_preview.py

@@ -195,7 +195,7 @@ def __create_new_preview_env(
 def __create_pullrequest(branch, gitops_config, root_git):
     title = "Updated preview environment for " + gitops_config.application_name
     description = f"""
-This Pull Request is automatically created through [gitopscli](https://github.com/baloise-incubator/gitopscli).
+This Pull Request is automatically created through [gitopscli](https://github.com/baloise/gitopscli).
 """
     pull_request = root_git.create_pull_request(branch, "master", title, description)
     logging.info("Pull request created: %s", {root_git.get_pull_request_url(pull_request)})

gitopscli/commands/delete_preview.py

@@ -92,7 +92,7 @@ def delete_preview_command(
 def __create_pullrequest(branch, gitops_config, root_git):
     title = "Deleted preview environment for " + gitops_config.application_name
     description = f"""
-This Pull Request is automatically created through [gitopscli](https://github.com/baloise-incubator/gitopscli).
+This Pull Request is automatically created through [gitopscli](https://github.com/baloise/gitopscli).
 """
     pull_request = root_git.create_pull_request(branch, "master", title, description)
     logging.info("Pull request created: %s", {root_git.get_pull_request_url(pull_request)})

mkdocs.yml

@@ -1,11 +1,11 @@
 # Project information
 site_name: 'GitOps CLI'
 site_description: 'A command line interface to perform operations on GitOps managed infrastructure repositories.'
-site_url: 'https://baloise-incubator.github.io/gitopscli/'
+site_url: 'https://baloise.github.io/gitopscli/'
 
 # Repository
-repo_name: 'baloise-incubator/gitopscli'
-repo_url: 'https://github.com/baloise-incubator/gitopscli'
+repo_name: 'baloise/gitopscli'
+repo_url: 'https://github.com/baloise/gitopscli'
 
 # Navigation
 nav: