Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

other: Provide option to add environment variables to only supersetNode #16627

Merged
merged 6 commits into from
Sep 17, 2021

Conversation

dd-willgan
Copy link
Contributor

SUMMARY

I'm adding an option to only add env variables to the main supersetNode pod through the Helm chart. See #16625.

TESTING INSTRUCTIONS

I added some test values in values.yaml and confirmed that they were being read properly locally.

ADDITIONAL INFORMATION

  • Has associated issue: Allow supersetNode in Helm chart to have its own ENV variables. #16625
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@rusackas rusackas requested a review from craig-rueda September 9, 2021 18:38
@dd-willgan dd-willgan changed the title #16625 Provide option to add environment variables to only supersetNode (other) Provide option to add environment variables to only supersetNode Sep 14, 2021
@dd-willgan dd-willgan changed the title (other) Provide option to add environment variables to only supersetNode other: Provide option to add environment variables to only supersetNode Sep 14, 2021
@junlincc junlincc requested a review from dpgaspar September 15, 2021 18:21
@@ -79,6 +79,12 @@ spec:
value: {{ $value | quote }}
{{- end }}
{{- end }}
{{- if .Values.supersetNode.env }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this if necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dpgaspar No but after thinking about it I would prefer to keep it to match how extraEnv is read in this file and others.

@craig-rueda craig-rueda merged commit 7586e47 into apache:master Sep 17, 2021
opus-42 pushed a commit to opus-42/incubator-superset that referenced this pull request Nov 14, 2021
…de (apache#16627)

* Add env variables for supersetNode in Helm template

* Typo in template

* Removed unnecessary if

* Revert "Removed unnecessary if"

This reverts commit af83568.

* Bumping chart version to 0.3.8

Co-authored-by: Craig Rueda <[email protected]>
QAlexBall pushed a commit to QAlexBall/superset that referenced this pull request Dec 28, 2021
…de (apache#16627)

* Add env variables for supersetNode in Helm template

* Typo in template

* Removed unnecessary if

* Revert "Removed unnecessary if"

This reverts commit af83568.

* Bumping chart version to 0.3.8

Co-authored-by: Craig Rueda <[email protected]>
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 1.4.0 labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS 🚢 1.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants