viliproject / vili Goto Github PK

Today, Redis and Firebase are both required to deploy vili. Redis is used to store session metadata keyed by session tokens, and Firebase is used to store release metadata.

To simplify vili, it might make sense to remove the dependency on Firebase and implement release metadata storage on Redis.

When clicking on "Create" while creating a feature environment, the dialog box never closes or updates:

Instead, I have this error in the console:

This url api/v1/environments? returns a 500

Add support for watching changes in the cluster and pushing them to the frontend through websockets in order to get real-time status without needing a refresh.

Kubernetes Deployments support, please :)

This has been a red herring for a few people when trying to debug problems in feature environments. I'm not sure what this node status means, but it doesn't seem to be providing useful information.

Step 7. of the setup instructions states you should create a replication controller. The example link points to a 404.
I'm guessing that this is due to the change to a kubernetes deployment?
If so, the step wording should be changed and it should link to: https://github.com/airware/vili/blob/master/docs/examples/simple/deployment.yaml

Cheers,

Joe

After approving all apps for preproduction environment, the individual app list does not show that they are approved

Steps

1. Click approve all
2. Enter release notes
3. Hit OK

The all apps view does not reflect the approval and each individual app view does not reflect this as well

UI does not properly show the version of apps that have 0 replicas, due to the fact that replica sets don't get a revision from Kubernetes until they have at least 1 replica.

The Serverless Framework allows functions to be packaged into a directory, stored, and deployed in a separate step. This aligns well with CI/CD workflows, including the ones implemented in vili.

vili should support reading a repository of packaged functions (e.g. in S3), with a naming convention similar to docker tags (in a directory structure to mimic tags) and calling the serverless deploy command to deploy a given tag.

Hi, first of all, thanks for your work on this project!

It's cool find an open source Kubernetes CI+CD project written in Go!

I read all your documentation on the website and on GitHub. I still have some questions please:

1. Supposing that I create a feature/topic branch, should I use the vili interface to "register" the new branch? Or (supposing that I have already configured the integration with that GitHub repo) it's automagically detected and built? (we use the GitFlow approach)

2. Can you please describe a bit more the build process and available options? I mean, besides build the new Docker image and push it to Quay, could be possible hook some extra build steps that are external to the Docker image? (like prepare a new test database to connect to, etc)

Thank you very much in advance!

Save configmap state to github under the vili config directory and build a UI that will allow easy synchronization between the github config and the real state on the cluster.

would be handy to have bitbucket support

Create optional auth for vili and allow users to "log in" without Okta