kintoproj / kinto-dashboard Goto Github PK

Is your feature request related to a problem? Please describe.
Static website use to be running on our free tier. So it's automatically running with 2 replicas and there is no resources consumptions. On OSS, we should add it back.

Describe the solution you'd like
Enable the configuration panel for autoscaling and resources config for static website.
There might be a change to do on kinto-builder/deploy image.

• Clean repo from anything related to legacy KintoHub (non opensource)
• Make sure all dependencies are up to date with the new kintoproj organization
• Add documentation in README.md (what it is, requirements, how to run it, environment variables)
• Add automation with github actions (test/build/push/etc.)

Is your feature request related to a problem? Please describe.
Depending on proto files from a required 3rd party repo works great for internal-dev, but would prefer ease of use for open source.

Describe the solution you'd like
Create a new folder called proto and have a github submodule checkout and updated on new feature/bug releases when the proto file(s) have changed.

Describe alternatives you've considered
N/A

Additional context
N/A

Is your feature request related to a problem? Please describe.
Right now if the dashboard is not publicly exposed, we need to do kubectl port-forward both dashboard and core for users accessing the dashboard

Describe the solution you'd like
We should modify the Dockerfile to make it as a nginx container, serving both the static content and a proxy to the core API

Additional context
Make sure the grpc-web stream works for the proxy. (Be aware of the nginx idle timeout)

Describe the bug
On promoted services, modifying the cron pattern is not possible

To Reproduce
Steps to reproduce the behavior:

1. Create a 'job' service on a random environment and enable 'schedule cron job'
2. Tag the service after deployment is successful
3. Promote the service to another environment

Cron Pattern is disabled and you can't modify it

Expected behavior
I should be able to modify the cron pattern