Feature: Dashboard/Router without CI/CD integration

Expected Behaviour

Persona:

As an enterprise user I have my own opinionated way to do CI/CD and I've spent millions of dollars creating it. It's called Jenkins as a Service, or similar. It's been audited, passed security checks and has political buy-in. I don't want your Buildkit.

What do they lose vs. a fully integrated experience?

• CI
• CD
• GitHub / GitLab commit status integration
• Build logs integration

What can they gain?

If they deploy from their own CI/CD pipelines using the appropriate labels then they can access:

• A rich, new dashboard with integrated statistics
• The router for persona/org sub-domains
• OAuth2 authentication
• OAuth2 authorisation (partially finished/released)

Current Behaviour

Possible, yet undocumented. We could be missing out on many users who would benefit from the enhanced experience.

Possible Solution

Test what the minimum configuration would be and how to deploy it. Test it on functions deployed manually via the CLI or REST API.

See the example in the Dashboard README for how to correctly label/annotate functions: https://github.com/openfaas/openfaas-cloud/tree/master/dashboard#deploy-a-few-functions-for-sample-data