Problem

Provide a seamless experience for a developer to provide the code repo where their serverless function is defined, and have it deployed onto OpenShift, and visualized as a serverless function in Topology.

Acceptance Criteria

1. User can create a serverless function through the Import from Git flow, using the S2I flow.
2. The Create Serverless flow should use the same import from git flow, with the following exceptions
   1. Do not show the Resource types
   2. Change title 
3. This method is only available for the shipped runtimes, except for GO
4. Add a new Serverless functions card to Add page to support this new flow, displayed on an independent card (no title/header/grouping)
5. In existing Import from Git flow, allow the user to change Resource type if they wish (let's verify we want this) 
6. Allow users to view and possibly edit the environment variables which are shown in func.yaml
7. Users are able to visually identify the serverless function in the topology view (function.knative.dev label must be added to KSVC)
8. Add Telemetry
   1. Serverless functions card
   2. Upon clicking create, identify that a serverless function is being created

Spikes

1. ODC team will start with a spike & share the results with the larger ODC/Serverless team.  Need to use the func.yaml
2. ODC team will investigate how to handle the environment variables which are stored in the func.yaml & share the results with the larger ODC/Serverless team & make sure this is something they we would want to support.

MIRO

Questions

• If func.yaml is in the git repo, annotate it properly ... and don't show Resource Options, it should be Serverless Deployment
• Need to determine how this would work with customer provided builder images