* feature: ability to pull from your own docker registry using a secret
* feature: ability to pull from your own docker registry using a secret
* fix: formating
* fix: formating
* use secret for all deployments and jobs that use the helm chart
* update chart version number
Co-authored-by: jaisheel <jaisheel.mistry@partner.bmw.co.za>
* Add chart-action submodules
* use local github actions for chart actions
* Run actions checkout for local checkout
* Run lint when PR is edited
* Remove path filter and dummy value
* Fix fetch-depth
* Test chart version bump
* Update maintainer to pass validation
* Update maintainer to pass validation
* Create initial helm-release action for superset
* Add lintconf to ensure chart passes validation
* Add lint-test job
* Add apache licence headers
* Run job for master only
* Move helm-lint to separate workflow
* Helm release for master & helm dir changes only
* Dummy change to test linter
* Helm: no running as root by default
* Maintain for backwards compatibility
Reverted uid and script to work same way as they previously did to maintain backwards compatibility.
Added clarification in comments that this is not a recommended production configuration.
Co-authored-by: Stanislav Simovski <stanislav.simovski@elisa.fi>
* Make initial user configurable in helm chart
* Update helm/superset/values.yaml
Co-authored-by: Amit Miran <47772523+amitmiran137@users.noreply.github.com>
* Update helm/superset/values.yaml
Co-authored-by: Amit Miran <47772523+amitmiran137@users.noreply.github.com>
Co-authored-by: Craig Rueda <craig@craigrueda.com>
Co-authored-by: Amit Miran <47772523+amitmiran137@users.noreply.github.com>
* Add volume mapping for superset-extra-config
* Fix wrong type for VALUE, cannot use "." inside range.
Fixes Error: template: superset/templates/configmap-superset.yaml:30:16: executing "superset/templates/configmap-superset.yaml" at <.>: wrong type for value; expected chartutil.Values; got string
* feat: rename TABLE_NAMES_CACHE_CONFIG to DATA_CACHE_CONFIG
The corresponding cache will now also cache the query results.
* Slice use DATA_CACHE_CONFIG CACHE_DEFAULT_TIMEOUT
* Add test for default cache timeout
* rename FAR_FUTURE to ONE_YEAR_IN_SECS
