Support private project template repository

[Derek Li (derek1ee)]

Users

• Development manager tasked with ensuring a team is successful in using streaming data
• Developer on a team tasked with building new features using streaming data
• Developer at an org who manages a streaming platform while building new features that use streaming data
• Developer tasked with building pipelines for use in business analytics
• Other: [User type] tasked with [primary goal in the realm of streaming data]

Problems

1. Companies want to provide developers access, instead of/in addition of, the Confluent templates, an internal one.

Solutions

1. In the settings page, we can surface a text field that contains a comma-separated lists of template repo, by default including the Confluent one but allow users to add more.
2. What if companies do not wish to make the private template repo publicly accessible? How can auth be handled?
3. We also need to have a well documented instruction on what the template repo need to look like.

Goals

1. User can point to additional template repos to get more templates.
2. User clearly sees in the command palette when selecting template, differentiate templates from confluent vs. private repo.
3. Instrument when user configures/uses a private repo/template, but ensure to not log beyond that (e.g. no private repo url, no private template name).

Non-Goals

Background

Several customers ask

Proposal

N/A