From 095ac13330a13f739d113dcd03d7044ffcb55d16 Mon Sep 17 00:00:00 2001 From: Brian Giori Date: Fri, 1 Mar 2024 09:19:52 -0800 Subject: [PATCH] update to proxy v0.4.5 (#2) --- README.md | 19 ++++++++----------- charts/evaluation-proxy/Chart.yaml | 4 ++-- example/README.md | 7 +++---- example/values.yaml | 6 ++---- 4 files changed, 15 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index 475013a..5732806 100644 --- a/README.md +++ b/README.md @@ -28,23 +28,20 @@ The chart's `evaluationProxy` value contents exactly match the evaluation proxy' evaluationProxy: # At least one project is required. projects: - - id: "TODO" - apiKey: "TODO" + - apiKey: "TODO" secretKey: "TODO" - deploymentKeys: - - "TODO" + managementKey: "TODO" configuration: {} # redis: # uri: "redis://redis-master.default.svc.cluster.local:6379" ``` -| Value | Description | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `projects.id` | The Amplitude project ID. Can be found in the project's settings in Amplitude. | -| `projects.apiKey` | The project's API key. Can be found in the project's settings in Amplitude. | -| `projects.secretKey` | The project's secret key. Can be found in the project's settings in Amplitude. | -| `projects.deploymentKeys` | The deployment keys to manage. Listed deployment keys have associated flags and cohorts downloaded and managed by the proxy. The deployment keys listed here must be associated with the project identified in the other fields. | -| `configuration.redis.uri` | The uri for connecting to redis within the cluster. If missing, the proxy will run in memory. | +| Value | Description | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `projects.apiKey` | The project's API key. Can be found in the project's settings in Amplitude. | +| `projects.secretKey` | The project's secret key. Can be found in the project's settings in Amplitude. | +| `projects.managementKey` | The Experiment management api key. Must be created for the same project as the configured API and secret key. Used to automatically access and update deployments used for the project. | +| `configuration.redis.uri` | The uri for connecting to redis within the cluster. If missing, the proxy will run in memory. | ### Install chart diff --git a/charts/evaluation-proxy/Chart.yaml b/charts/evaluation-proxy/Chart.yaml index 0068e84..ff30d4e 100644 --- a/charts/evaluation-proxy/Chart.yaml +++ b/charts/evaluation-proxy/Chart.yaml @@ -9,10 +9,10 @@ sources: # 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.1 +version: 0.2.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. -appVersion: "0.2.0" +appVersion: "0.4.5" diff --git a/example/README.md b/example/README.md index 6ab3756..3070dd5 100644 --- a/example/README.md +++ b/example/README.md @@ -18,10 +18,9 @@ helm install -f redis-values.yaml redis bitnami/redis ## Configure `values.yaml` Update the fields in the `values.yaml` file: -1. `projects.id`: The Amplitude project ID. Can be found in the project's settings in Amplitude. -2. `projects.apiKey`: The project's API key. Can be found in the project's settings in Amplitude. -3. `projects.secretKey`: The project's secret key. Can be found in the project's settings in Amplitude. -4. `projects.deploymentKeys`: The deployment keys to manage. Listed deployment keys have associated flags and cohorts downloaded and managed by the proxy. The deployment keys listed here must be associated with the project identified in the other fields. +1. `projects.apiKey`: The project's API key. Can be found in the project's settings in Amplitude. +2. `projects.secretKey`: The project's secret key. Can be found in the project's settings in Amplitude. +3. `projects.managementKey`: The Experiment management api key. Must be created for the same project as the configured API and secret key. Used to automatically access and update deployments used for the project. ## Install Evaluation Proxy Helm Chart diff --git a/example/values.yaml b/example/values.yaml index fbd269d..b34ed58 100644 --- a/example/values.yaml +++ b/example/values.yaml @@ -1,10 +1,8 @@ evaluationProxy: projects: - - id: "TODO" - apiKey: "TODO" + - apiKey: "TODO" secretKey: "TODO" - deploymentKeys: - - "TODO" + managementKey: "TODO" configuration: redis: uri: "redis://redis-master.default.svc.cluster.local:6379"