determine project name from the root directory

Signed-off-by: Joe Lanford <[email protected]>

Author: joelanford

.taskfile.build.yaml

@@ -8,14 +8,14 @@ includes:
 vars:
   BIN: "{{.ROOT_DIR}}/bin"
   KUSTOMIZE_DIR: "config/default"
-  OPERATOR_CONTROLLER_MANIFEST: ./operator-controller.yaml
+  CONTROLLER_MANIFEST: ./{{.PROJECT}}.yaml
 
   OLMV0_VERSION: v0.24.0
   CERT_MANAGER_VERSION: v1.9.0
   RUKPAK_VERSION: v0.11.0
 
 env:
-  IMAGE_REPO: quay.io/operator-framework/operator-controller
+  IMAGE_REPO: quay.io/operator-framework/{{.PROJECT}}
   IMAGE_TAG: devel
 
 tasks:
@@ -58,7 +58,7 @@ tasks:
       GOARCH is taken from the environment to ensure a binary that will run on the local
       machine. GOOS is always set to `linux` for the docker build.
       
-      By default, the image is tagged as quay.io/operator-framework/operator-controller:devel.
+      By default, the image is tagged as quay.io/operator-framework/{{.PROJECT}}:devel.
       You can control the image repo and tag by setting the IMAGE_REPO and IMAGE_TAG
       environment variables.
     cmds:
@@ -79,17 +79,17 @@ tasks:
       with the controller image set to the IMAGE_REPO and IMAGE_TAG environment variables.
     cmds:
       - cd config/manager && {{.TOOLSBIN}}/kustomize edit set image controller=$IMAGE_REPO:$IMAGE_TAG
-      - "{{.TOOLSBIN}}/kustomize build {{.KUSTOMIZE_DIR}} > {{.OPERATOR_CONTROLLER_MANIFEST}}"
+      - "{{.TOOLSBIN}}/kustomize build {{.KUSTOMIZE_DIR}} > {{.CONTROLLER_MANIFEST}}"
     deps: [tools:kustomize, generate]
 
   install-script:
     desc: "Generate the install script"
     summary: |
       This task generates the install script that can be used to install the operator.
       
-      The OPERATOR_CONTROLLER_MANIFEST task variable is used to set the location that
-      will be used to `kubectl apply -f` the operator-controller manifest. By default,
-      this is set to `./operator-controller.yaml`. However this can be overridden during
+      The CONTROLLER_MANIFEST task variable is used to set the location that
+      will be used to `kubectl apply -f` the controller manifest. By default,
+      this is set to `./{{.PROJECT}}.yaml`. However this can be overridden during
       a release to reference the release manifest URL that is uploaded to GitHub during
       the release.
     silent: true
@@ -113,8 +113,8 @@ tasks:
         kubectl wait --for=condition=Available --namespace=rukpak-system deployment/rukpak-webhooks --timeout=60s
         kubectl wait --for=condition=Available --namespace=crdvalidator-system deployment/crd-validation-webhook --timeout=60s
 
-        # Install operator-controller
-        kubectl apply -f {{.OPERATOR_CONTROLLER_MANIFEST}}
-        kubectl wait --for=condition=Available --namespace=operator-controller-system deployment/operator-controller-controller-manager --timeout=60s
+        # Install controller
+        kubectl apply -f {{.CONTROLLER_MANIFEST}}
+        kubectl wait --for=condition=Available --namespace={{.PROJECT}}-system deployment/{{.PROJECT}}-controller-manager --timeout=60s
         EOF
       - chmod +x ./install.sh

.taskfile.deploy.yaml

@@ -24,10 +24,10 @@ tasks:
       - task: build:manifest
         vars:
           KUSTOMIZE_DIR: "{{.KUSTOMIZE_DIR}}"
-          OPERATOR_CONTROLLER_MANIFEST: "{{.OPERATOR_CONTROLLER_MANIFEST}}"
+          CONTROLLER_MANIFEST: "{{.CONTROLLER_MANIFEST}}"
       - task: build:install-script
         vars:
-          OPERATOR_CONTROLLER_MANIFEST: "{{.OPERATOR_CONTROLLER_MANIFEST}}"
+          CONTROLLER_MANIFEST: "{{.CONTROLLER_MANIFEST}}"
       - task: kind:create
         vars:
           KIND_CLUSTER_NAME: "{{.KIND_CLUSTER_NAME}}"

.taskfile.kind.yaml

@@ -1,7 +1,7 @@
 version: '3'
 
 vars:
-  KIND_CLUSTER_NAME: "operator-controller"
+  KIND_CLUSTER_NAME: "{{.PROJECT}}"
 
 includes:
   tools:

.taskfile.test.yaml

@@ -83,7 +83,7 @@ tasks:
       - task: deploy:kind
         vars:
           KUSTOMIZE_DIR: "config/e2e"
-          OPERATOR_CONTROLLER_MANIFEST: "operator-controller-e2e.yaml"
+          CONTROLLER_MANIFEST: "{{.PROJECT}}-e2e.yaml"
           KIND_CLUSTER_NAME: "{{.KIND_CLUSTER_NAME}}-e2e"
           KIND_EXTRA_FLAGS: "--config ./kind-e2e.yaml"
           GO_COVER: "true"
@@ -93,8 +93,8 @@ tasks:
             KIND_CLUSTER_NAME: "{{.KIND_CLUSTER_NAME}}-e2e"
       - "{{.TOOLSBIN}}/ginkgo --tags {{.GO_BUILD_TAGS}} --progress --trace {{with .FOCUS}}--focus '{{.}}'{{end}} ./test/e2e"
 
-      # Delete the operator controller manager pod to write the coverage data to disk.
-      - kubectl delete --wait pod -n operator-controller-system -l control-plane=controller-manager
+      # Delete the controller manager pod to write the coverage data to disk.
+      - kubectl delete --wait pod -n {{.PROJECT}}-system -l control-plane=controller-manager
       - go tool covdata percent -i={{.GOCOVERDIR}}
     deps: [tools:ginkgo]
 

Taskfile.dist.yaml

@@ -1,11 +1,12 @@
 version: '3'
 
 vars:
+  PROJECT: "{{base .ROOT_DIR}}"
   TOOLSBIN: "{{.ROOT_DIR}}/hack/tools/bin"
   GO_BUILD_TAGS: upstream
 
 env:
-  IMAGE_REPO: quay.io/operator-framework/operator-controller
+  IMAGE_REPO: quay.io/operator-framework/{{.PROJECT}}
   IMAGE_TAG: devel
 
   GORELEASER_ARGS: --snapshot --clean
@@ -39,7 +40,7 @@ tasks:
         This task will run the operator in a kind cluster.
       
         The KIND_CLUSTER_NAME task variable is used to control the name of the
-        kind cluster. By default, this is set to "operator-controller".
+        kind cluster. By default, this is set to "{{.PROJECT}}".
     cmds:
       - task: deploy:kind
         vars:
@@ -64,6 +65,6 @@ tasks:
       - task: build:manifest
       - task: build:install-script
         vars:
-          OPERATOR_CONTROLLER_MANIFEST: https://github.com/operator-framework/operator-controller/releases/download/$IMAGE_TAG/operator-controller.yaml
+          CONTROLLER_MANIFEST: https://github.com/operator-framework/{{.PROJECT}}/releases/download/$IMAGE_TAG/{{.PROJECT}}.yaml
       - "{{.TOOLSBIN}}/goreleaser release $GORELEASER_ARGS"
     deps: [tools:goreleaser]