Replace all occurrences of previous repository path in the codebase

Author: mkubaczyk

.circleci/config.yml

@@ -17,7 +17,7 @@ jobs:
     docker:
       - image: goreleaser/goreleaser
         entrypoint: /bin/bash
-    working_directory: "/go/src/github.com/Praqma/helmsman"
+    working_directory: "/go/src/github.com/mkubaczyk/helmsman"
     steps:
       - run:
           name: install git

CONTRIBUTION.md

@@ -7,7 +7,7 @@ Pull requests, feeback/feature requests are all welcome. This guide will be upda
 To build helmsman from source, you need go:1.17+. Follow the steps below:
 
 ```sh
-git clone https://github.com/Praqma/helmsman.git
+git clone https://github.com/mkubaczyk/helmsman.git
 make tools # installs few tools for testing, building, releasing
 make build
 make test

Dockerfile

@@ -55,7 +55,7 @@ COPY --from=helm-installer /usr/local/bin/helm /usr/local/bin/helm
 COPY --from=helm-installer /root/.cache/helm/plugins/ /root/.cache/helm/plugins/
 COPY --from=helm-installer /root/.local/share/helm/plugins/ /root/.local/share/helm/plugins/
 
-WORKDIR /go/src/github.com/Praqma/helmsman
+WORKDIR /go/src/github.com/mkubaczyk/helmsman
 
 COPY . .
 RUN make test \
@@ -79,4 +79,4 @@ COPY --from=helm-installer /usr/local/bin/sops /usr/local/bin/sops
 COPY --from=helm-installer /root/.cache/helm/plugins/ /root/.cache/helm/plugins/
 COPY --from=helm-installer /root/.local/share/helm/plugins/ /root/.local/share/helm/plugins/
 
-COPY --from=builder /go/src/github.com/Praqma/helmsman/helmsman /bin/helmsman
+COPY --from=builder /go/src/github.com/mkubaczyk/helmsman/helmsman /bin/helmsman

README.md

@@ -1,4 +1,4 @@
-[![GitHub version](https://d25lcipzij17d.cloudfront.net/badge.svg?id=gh&type=6&v=v3.18.0&x2=0)](https://github.com/Praqma/helmsman/releases) [![CircleCI](https://circleci.com/gh/Praqma/helmsman/tree/master.svg?style=svg)](https://circleci.com/gh/Praqma/helmsman/tree/master)
+[![GitHub version](https://d25lcipzij17d.cloudfront.net/badge.svg?id=gh&type=6&v=v3.18.0&x2=0)](https://github.com/mkubaczyk/helmsman/releases) [![CircleCI](https://circleci.com/gh/Praqma/helmsman/tree/master.svg?style=svg)](https://circleci.com/gh/Praqma/helmsman/tree/master)
 
 ![helmsman-logo](docs/images/helmsman.png)
 
@@ -17,10 +17,10 @@ Thank you for your patience and trusting Helmsman with your tasks!
 
 # How does it work?
 
-Helmsman uses a simple declarative [TOML](https://github.com/toml-lang/toml) file to allow you to describe a desired state for your k8s applications as in the [example toml file](https://github.com/Praqma/helmsman/blob/master/examples/example.toml).
-Alternatively YAML declaration is also acceptable [example yaml file](https://github.com/Praqma/helmsman/blob/master/examples/example.yaml).
+Helmsman uses a simple declarative [TOML](https://github.com/toml-lang/toml) file to allow you to describe a desired state for your k8s applications as in the [example toml file](https://github.com/mkubaczyk/helmsman/blob/master/examples/example.toml).
+Alternatively YAML declaration is also acceptable [example yaml file](https://github.com/mkubaczyk/helmsman/blob/master/examples/example.yaml).
 
-The desired state file (DSF) follows the [desired state specification](https://github.com/Praqma/helmsman/blob/master/docs/desired_state_specification.md).
+The desired state file (DSF) follows the [desired state specification](https://github.com/mkubaczyk/helmsman/blob/master/docs/desired_state_specification.md).
 
 Helmsman sees what you desire, validates that your desire makes sense (e.g. that the charts you desire are available in the repos you defined), compares it with the current state of Helm and figures out what to do to make your desire come true.
 
@@ -78,15 +78,15 @@ Please make sure the following are installed prior to using `helmsman` as a bina
 - [helm](https://github.com/helm/helm) (helm >=v2.10.0 for `helmsman` >= 1.6.0, helm >=v3.0.0 for `helmsman` >=v3.0.0)
 - [helm-diff](https://github.com/databus23/helm-diff) (`helmsman` >= 1.6.0)
 
-If you use private helm repos, you will need either `helm-gcs` or `helm-s3` plugin or you can use basic auth to authenticate to your repos. See the [docs](https://github.com/Praqma/helmsman/blob/master/docs/how_to/helm_repos) for details.
+If you use private helm repos, you will need either `helm-gcs` or `helm-s3` plugin or you can use basic auth to authenticate to your repos. See the [docs](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/helm_repos) for details.
 
-Check the [releases page](https://github.com/Praqma/Helmsman/releases) for the different versions.
+Check the [releases page](https://github.com/mkubaczyk/helmsman/releases) for the different versions.
 
 ```sh
 # on Linux
-curl -L https://github.com/Praqma/helmsman/releases/download/v3.18.0/helmsman_3.18.0_linux_amd64.tar.gz | tar zx
+curl -L https://github.com/mkubaczyk/helmsman/releases/download/v3.18.0/helmsman_3.18.0_linux_amd64.tar.gz | tar zx
 # on MacOS
-curl -L https://github.com/Praqma/helmsman/releases/download/v3.18.0/helmsman_3.18.0_darwin_amd64.tar.gz | tar zx
+curl -L https://github.com/mkubaczyk/helmsman/releases/download/v3.18.0/helmsman_3.18.0_darwin_amd64.tar.gz | tar zx
 
 mv helmsman /usr/local/bin/helmsman
 ```
@@ -114,19 +114,19 @@ asdf install helmsman latest
 
 # Documentation
 
-> Documentation for Helmsman v1.x can be found at: [docs v1.x](https://github.com/Praqma/helmsman/tree/1.x/docs)
+> Documentation for Helmsman v1.x can be found at: [docs v1.x](https://github.com/mkubaczyk/helmsman/tree/1.x/docs)
 
-- [How-Tos](https://github.com/Praqma/helmsman/blob/master/docs/how_to/).
-- [Desired state specification](https://github.com/Praqma/helmsman/blob/master/docs/desired_state_specification.md).
-- [CMD reference](https://github.com/Praqma/helmsman/blob/master/docs/cmd_reference.md)
+- [How-Tos](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/).
+- [Desired state specification](https://github.com/mkubaczyk/helmsman/blob/master/docs/desired_state_specification.md).
+- [CMD reference](https://github.com/mkubaczyk/helmsman/blob/master/docs/cmd_reference.md)
 
 ## Usage
 
 Helmsman can be used in three different settings:
 
-- [As a binary with a hosted cluster](https://github.com/Praqma/helmsman/blob/master/docs/how_to/settings).
-- [As a docker image in a CI system or local machine](https://github.com/Praqma/helmsman/blob/master/docs/how_to/deployments/ci.md) Always use a tagged docker image from [dockerhub](https://hub.docker.com/r/praqma/helmsman/) as the `latest` image can (at times) be unstable.
-- [As a docker image inside a k8s cluster](https://github.com/Praqma/helmsman/blob/master/docs/how_to/deployments/inside_k8s.md)
+- [As a binary with a hosted cluster](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/settings).
+- [As a docker image in a CI system or local machine](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/deployments/ci.md) Always use a tagged docker image from [dockerhub](https://hub.docker.com/r/praqma/helmsman/) as the `latest` image can (at times) be unstable.
+- [As a docker image inside a k8s cluster](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/deployments/inside_k8s.md)
 
 # Contributing
 

cmd/helmsman/main.go

@@ -3,7 +3,7 @@ package main
 import (
 	"os"
 
-	"github.com/Praqma/helmsman/internal/app"
+	"github.com/mkubaczyk/helmsman/internal/app"
 )
 
 func main() {

docs/how_to/apps/basic.md

@@ -6,7 +6,7 @@ version: v3.0.0-beta5
 
 ## Install releases
 
-You can run helmsman with the [example.toml](https://github.com/Praqma/helmsman/blob/master/examples/example.toml) or [example.yaml](https://github.com/Praqma/helmsman/blob/master/examples/example.yaml) file.
+You can run helmsman with the [example.toml](https://github.com/mkubaczyk/helmsman/blob/master/examples/example.toml) or [example.yaml](https://github.com/mkubaczyk/helmsman/blob/master/examples/example.yaml) file.
 
 ```shell
 $ helmsman --apply -f example.toml

docs/how_to/apps/destroy.md

@@ -8,5 +8,5 @@ Helmsman allows you to delete all the helm releases that were deployed by Helmsm
 
 The `--destroy` flag will remove all deployed releases from a given desired state file (DSF). Note that this does not currently delete the namespaces nor the Kubernetes contexts created.
 
-This was originally requested in issue [#88](https://github.com/Praqma/helmsman/issues/88).
+This was originally requested in issue [#88](https://github.com/mkubaczyk/helmsman/issues/88).
 

docs/how_to/apps/lifecycle_hooks.md

@@ -139,11 +139,11 @@ You can do that by setting `deleteOnSuccess` to true in the `globalHooks` stanza
 
 You can expand variables/parameters in the hook manifests at run time in one of the following ways:
 
-- use env variables (defined as `$MY_VAR` in your manifests) and run helmsman with `--subst-env-values`. Environment variables can be read from the environment or you can [load them from an env file](https://github.com/Praqma/helmsman/blob/master/docs/how_to/apps/secrets.md#passing-secrets-from-env-files)
+- use env variables (defined as `$MY_VAR` in your manifests) and run helmsman with `--subst-env-values`. Environment variables can be read from the environment or you can [load them from an env file](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/apps/secrets.md#passing-secrets-from-env-files)
 
 - use [AWS SSM parameters](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) (defined as `{{ssm: MY_PARAM }}` in your manifests) and run helmsman with `--subst-ssm-values`.
 
-- Pass encrypted values with [hiera-eyaml](https://github.com/Praqma/helmsman/blob/master/docs/how_to/settings/use-hiera-eyaml-as-secrets-encryption.md)
+- Pass encrypted values with [hiera-eyaml](https://github.com/mkubaczyk/helmsman/blob/master/docs/how_to/settings/use-hiera-eyaml-as-secrets-encryption.md)
 
 ## Limitations
 

docs/how_to/apps/override_context_from_cmd.md

@@ -6,7 +6,7 @@ version: v3.2.0
 
 There are two main use cases for this flag:
 
-1. To speed up Helmsman's execution when you have too many release (see [issue #418](https://github.com/Praqma/helmsman/issues/418))
+1. To speed up Helmsman's execution when you have too many release (see [issue #418](https://github.com/mkubaczyk/helmsman/issues/418))
    This flag works by skipping the search for the context information which Helmsman adds in the form of labels to the helm release state (secrets/configmaps). 
 
    > Use this option with caution. You must be sure that this won't cause conflicts.

docs/how_to/misc/migrate_to_3.md

@@ -16,8 +16,8 @@ The migration process can go as follows:
 > At this stage, Helm v3 can see and operate on your releases, but Helmsman can't. This is because Helmsman defined labels haven't been migrated to the Helm v3 releases state.
 
 ## Migrate to Helmsman v3.x
-- Download the latest Helmsman v3.x release from [Github releases](https://github.com/Praqma/helmsman/releases) 
-- Modify your Helmsman's TOML/YAML desired state files (DSFs) to be Helmsman v3.x compatible. You can check [v3.0.0 release notes](https://github.com/Praqma/helmsman/blob/v3.0.0/release-notes.md) for what's changed and verify from the [Desired State Spec](https://github.com/Praqma/helmsman/blob/master/docs/desired_state_specification.md) that your DSF files are compatible. 
+- Download the latest Helmsman v3.x release from [Github releases](https://github.com/mkubaczyk/helmsman/releases) 
+- Modify your Helmsman's TOML/YAML desired state files (DSFs) to be Helmsman v3.x compatible. You can check [v3.0.0 release notes](https://github.com/mkubaczyk/helmsman/blob/v3.0.0/release-notes.md) for what's changed and verify from the [Desired State Spec](https://github.com/mkubaczyk/helmsman/blob/master/docs/desired_state_specification.md) that your DSF files are compatible. 
 
 > Everything related to Tiller will be removed from your DSFs at this stage.