feat: bump external dependencies versions to >= 1.0.0

merchant-registry-svc/Chart.yaml

@@ -13,13 +13,13 @@ dependencies:
     version: ">= 1.0.0"
     repository: file://./chart-acquirer-frontend
   - name: chart-merchant-db
-    version: 0.1.0
+    version: ">= 1.0.0"
     repository: file://./chart-merchant-db
   - name: chart-minio
-    version: 0.1.0
+    version: ">= 1.0.0"
     repository: file://./chart-minio
   - name: chart-rabbitmq
-    version: 0.1.0
+    version: ">= 1.0.0"
     repository: file://./chart-rabbitmq
   - name: chart-registry-oracle
     version: ">= 1.0.0"

merchant-registry-svc/chart-merchant-db/Chart.yaml

@@ -1,24 +1,6 @@
 apiVersion: v2
 name: chart-merchant-db
-description: A Helm chart for Kubernetes
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+description: MySQL database for Merchant Registry
 type: application
-
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
+version: 1.0.0
 appVersion: "1.16.0"

merchant-registry-svc/chart-minio/Chart.yaml

@@ -1,24 +1,6 @@
 apiVersion: v2
 name: chart-minio
-description: A Helm chart for Kubernetes
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+description: MinIO chart for Merchant Registry
 type: application
-
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
+version: 1.0.0
 appVersion: "1.16.0"

merchant-registry-svc/chart-rabbitmq/Chart.yaml

@@ -1,24 +1,6 @@
 apiVersion: v2
 name: chart-rabbitmq
-description: A Helm chart for Kubernetes
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+description: RabbitMQ chart for Merchant Registry
 type: application
-
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
+version: 1.0.0
 appVersion: "1.16.0"