Skip to content
This repository has been archived by the owner on Jan 26, 2023. It is now read-only.

Duplicate ALLURE_CRYPTO_PASSWORD in Deployments #26

Open
dyurchenko-whoosh opened this issue Apr 1, 2022 · 0 comments
Open

Duplicate ALLURE_CRYPTO_PASSWORD in Deployments #26

dyurchenko-whoosh opened this issue Apr 1, 2022 · 0 comments

Comments

@dyurchenko-whoosh
Copy link

Hi,

In docs values ALLURE_CRYPTO_PASSWORD set in value uaa.env.secret and report.env.secret, which after running helm appear in Deployment template:

<cut>
          - name: "ALLURE_CRYPTO_PASSWORD"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "uaa.ALLURE_CRYPTO_PASSWORD"
<cut>

And same for report:

<cut>
          - name: "ALLURE_CRYPTO_PASSWORD"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "report.ALLURE_CRYPTO_PASSWORD"
<cut>

In commit 9fb927d you add env ALLURE_CRYPTO_PASSWORD with different key ref:

+         - name: "ALLURE_CRYPTO_PASSWORD"
+           valueFrom:
+             secretKeyRef:
+               name: allure-ee-allure-ee
+               key: "password"

So in resulting Deployment template duplicates are occurred with name ALLURE_CRYPTO_PASSWORD and different refs:

$ helm diff upgrade --reuse-values allure-ee qameta/allure-ee
<cut>
          - name: "SPRING_SESSION_STORE_TYPE"
            value: "REDIS"
+         - name: "ALLURE_CRYPTO_PASSWORD"
+           valueFrom:
+             secretKeyRef:
+               name: allure-ee-allure-ee
+               key: "password"
          - name: "ALLURE_BLOBSTORAGE_S3_ACCESSKEY"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "report.ALLURE_BLOBSTORAGE_S3_ACCESSKEY"
          - name: "ALLURE_BLOBSTORAGE_S3_SECRETKEY"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "report.ALLURE_BLOBSTORAGE_S3_SECRETKEY"
          - name: "ALLURE_CRYPTO_PASSWORD"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "report.ALLURE_CRYPTO_PASSWORD"
          - name: "ALLURE_REDIS_NAMESPACE"
            valueFrom:
              secretKeyRef:
                name: allure-ee-allure-ee
                key: "report.ALLURE_REDIS_NAMESPACE"
<cut>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant