Merge pull request #203 from omeryahud/update-repo-after-migration

Updated references and import paths to the new repository location

Author: omeryahud

README.md

@@ -66,7 +66,7 @@ The `kubevirt-ssp-operator` provides three way to consume its manifests
    If you want to install the `kubevirt-ssp-operator` *without* HCO, please use the `hack/install-operator.sh` helper.
 2. CSVs and manifests to be used with HCO. HCO is the preferred way to deploy the `kubevirt-ssp-operator`.
    We provide CSV file and package file (and everything else), autogenerated on release using `make manifests`.
-   These manifests are available for download in the [release page](https://github.com/MarSik/kubevirt-ssp-operator/releases).
+   These manifests are available for download in the [release page](https://github.com/kubevirt/kubevirt-ssp-operator/releases).
    This step creates both the unversioned CSV (see below) and the versioned -per release CSV. This is because...
 3. Recent HCO prefer to consume the CSV from the container images, using the `org.kubevirt.hco.csv-generator.v1` LABEL
    entrypoint. The HCO build process will invoke the script on each container, expecting an up to date, dynamically generated

build/generate.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 ./vendor/k8s.io/code-generator/generate-groups.sh \
 	all \
-	github.com/MarSik/kubevirt-ssp-operator/pkg/client \
-	github.com/MarSik/kubevirt-ssp-operator/pkg/apis \
+	github.com/kubevirt/kubevirt-ssp-operator/pkg/client \
+	github.com/kubevirt/kubevirt-ssp-operator/pkg/apis \
 	kubevirt:v1

docs/dev/status-conditions.md

@@ -62,7 +62,7 @@ Degraded - False
 
 6. you can of course delete pods and test if it changes conditions (but take in account, every iteration is slow, so when you delete e.g. node-labeller, it can be recreated between the iterations and ansible will not notice that it was deleted).
 The Easiest way is to create e.g. 2 nodes, let node-labeller to be deployed on both nodes and then disable one (`sudo ifconfig eth0 down && sleep 10 && sudo ifconfig eth0 up`)
-and then wait for [300x10 second](https://github.com/MarSik/kubevirt-ssp-operator/pull/76/files#diff-d1fae8c4046ebdb431e9b097881fc1b7R39 I think we should lower this constant) after that it should set conditions:
+and then wait for [300x10 second](https://github.com/kubevirt/kubevirt-ssp-operator/pull/76/files#diff-d1fae8c4046ebdb431e9b097881fc1b7R39 I think we should lower this constant) after that it should set conditions:
 ```
 Progressing - True
 Available - False

hack/get-operator-tag.sh

@@ -11,5 +11,5 @@ if [ -n "${TRAVIS_TAG}" ]; then
 	echo "${TRAVIS_TAG}"
 else
 	# refreshing manifests, getting the last stable tag
-	_curl -s 'https://api.github.com/repos/MarSik/kubevirt-ssp-operator/tags' | jq -r '.[].name' | sort -r | head -1
+	_curl -s 'https://api.github.com/repos/kubevirt/kubevirt-ssp-operator/tags' | jq -r '.[].name' | sort -r | head -1
 fi

hack/install-operator.sh

@@ -18,7 +18,7 @@ LAST_TAG=""
 if [ "${CI}" != "true" ] || [ "${TRAVIS}" != "true" ]; then
 	# TODO: consume releases, not tags
 	# TODO: check if the github APIs guarantee the ordering
-	LAST_TAG=$( _curl -s https://api.github.com/repos/MarSik/kubevirt-ssp-operator/tags | jq -r '.[].name' | sort -rV | head -1 )
+	LAST_TAG=$( _curl -s https://api.github.com/repos/kubevirt/kubevirt-ssp-operator/tags | jq -r '.[].name' | sort -rV | head -1 )
 fi
 
 oc create -n ${NAMESPACE} -f ${BASEPATH}/../deploy/service_account.yaml

pkg/apis/addtoscheme_kubevirt_v1.go

@@ -1,7 +1,7 @@
 package apis
 
 import (
-	"github.com/MarSik/kubevirt-ssp-operator/pkg/apis/kubevirt/v1"
+	"github.com/kubevirt/kubevirt-ssp-operator/pkg/apis/kubevirt/v1"
 )
 
 func init() {