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

feat: add scheduler #51

Closed
wants to merge 5 commits into from
Closed

feat: add scheduler #51

wants to merge 5 commits into from

Conversation

rephus
Copy link
Contributor

@rephus rephus commented Apr 19, 2023

image

image

@@ -0,0 +1,69 @@
apiVersion: apps/v1
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've only added a deployment, I guess the ConfigMap is the same than lightdash

key: {{ (include "lightdash.database.secret.passwordKey" .) }}
envFrom:
- configMapRef:
name: {{ .Release.Name }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

using the same lightdash configmap by using .Release.Name

@rephus rephus requested a review from owlas April 19, 2023 14:32
@@ -8,5 +8,8 @@ dependencies:
- name: browserless-chrome
repository: https://charts.sagikazarmark.dev
version: 0.0.4
digest: sha256:e67eebb04f4ad84367593b74cf5dd71a4ee8e5daede54549be6dfea396419064
generated: "2023-01-11T20:11:55.264423Z"
- name: scheduler
Copy link
Contributor

Choose a reason for hiding this comment

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

can we call this lightdash-scheduler so it's obviously a lightdash-specific dependency

@@ -27,6 +27,7 @@ configMap:
DBT_PROJECT_DIR: ""
# -- Public URL of your instance including protocol e.g. https://lightdash.myorg.com
SITE_URL: ""
LIGHTDASH_SECRET: 'secret'
Copy link
Contributor

Choose a reason for hiding this comment

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

This might be dangerous because by default everybody will use the same encryption key. I think it's better to throw an error if this isn't set. What was the original behaviour?

@@ -53,6 +54,7 @@ If you don't want helm to manage this, you may wish to separately create a secre
| autoscaling.targetCPUUtilizationPercentage | int | `80` | |
| backendConfig.create | bool | `false` | |
| browserless-chrome.enabled | bool | `true` | |
| browserless-chrome.env.CONNECTION_TIMEOUT | string | `"180000"` | |
Copy link
Contributor

Choose a reason for hiding this comment

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

do you know why this appeared here?

digest: sha256:e67eebb04f4ad84367593b74cf5dd71a4ee8e5daede54549be6dfea396419064
generated: "2023-01-11T20:11:55.264423Z"
- name: scheduler
repository: ""
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this can be a file uri file://scheduler or something

@owlas owlas closed this Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants