chart changes to trigger a cr run

.drone.yml

@@ -43,3 +43,32 @@ steps:
       - push
       - pull_request
       - cron
+---
+kind: pipeline
+type: kubernetes
+name: release-bitwarden-crd-operator
+
+platform:
+  os: linux
+  arch: amd64
+
+steps:
+  - name: release-bitwarden-crd-operator
+    image: plugins/kaniko
+    settings:
+      dockerfile: Dockerfile
+      password:
+        from_secret: docker_password
+      username:
+        from_secret: docker_username
+      repo: lerentis/bitwarden-crd-operator
+      tags:
+        - latest
+        - ${DRONE_TAG##v}
+    when:
+      event:
+      - tag
+    resources:
+      limits:
+        cpu: 200
+        memory: 1024MiB

README.md

@@ -77,6 +77,6 @@ type: Opaque
 
 [] support more types  
 [] offer option to use a existing secret in helm chart  
-[] host chart on gh pages  
-[] write release pipeline  
+[x] host chart on gh pages  
+[x] write release pipeline  
 [x] maybe extend spec to offer modification of keys as well

charts/bitwarden-crd-operator/Chart.yaml

@@ -4,6 +4,6 @@ description: Deploy the Bitwarden CRD Operator
 
 type: application
 
-version: 0.1.0
+version: 0.1.1
 
-appVersion: "0.1.0"
+appVersion: "0.1.1"

charts/bitwarden-crd-operator/templates/NOTES.txt

@@ -1 +1,2 @@
-Have fun :) 
+Bitwarden CRD Operator has been deployed. 
+Go ahead and create some secrets directly from bitwarden

charts/bitwarden-crd-operator/values.yaml

@@ -8,7 +8,7 @@ image:
   repository: lerentis/bitwarden-crd-operator
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "5806fb6c54c024ec918eac97601880096b5ff1d9"
+  # tag: "0.1.0"
 
 imagePullSecrets: []
 nameOverride: ""