Dexter John Genterone
Dexter John Genterone
i don't think we'll be needing that soon.
can we close this?
An idea of a user profile might look like this: ``` kontinuous: users: - {uuid} - name: username, taken from sub of jwt or github/bitbucket ID? keys: github: _encrypted_github_key_ bitbucket:...
related: for web login via github, bitbucket, etc:  for oidc login, eg. auth0:  ps. mermaid-cli is sooo cool.
a few things to note about user and authentication: 1. need a way to add identities to an existing user (eg. user uses github login, a new user gets created...
login auth and user now follow this pattern. it should be easier to add new login now (bitbucket)
is this for the kon5s services or the jobs in general?
the readiness probe might be useful for the running jobs. :)
This would probably tie in with the Controller Refactor. Also removes the need for us to start our own etcd instance.
Yes. Thinking about pipelines, stages, and build info would be stored as ThirdPartyResources and it's up to the controllers to monitor the api for changes to start builds, send notifications,...