You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extension reveals developer related resources like:
Components (s2i, devfile)
Component versions (s2i)
Starter Projects (devile)
in the middle of workflow. To get to that point way to many requirements should be fulfilled first like, being logged to the cluster, have context folder ready in workspace and etc. If developer is not logged into cluster it is not even possible to see what we have.
Extension should provide the view where all resources presented as a tree and has context menu/default commands to trigger workflow to use that item to create s2i component with specific version and or a devfile component based on local workspace folder with sources or specific starter project if workspace folder is empty.
For S2I Component Version and Starter Project nodes there should be commands to make it simple to look at the example code we have in git or any kind of source control:
Open Sample Project Repository in browser
Clone Sample Project Repository to workspace
For S2I Component Type Tags, Devfile Component Type and starter project there should be 'New Component' command to create component using that specific component and for devfile components starter project. For s2i components you can first clone sample project into workspace and then use it as context folder when creating component.
The text was updated successfully, but these errors were encountered:
Extension reveals developer related resources like:
in the middle of workflow. To get to that point way to many requirements should be fulfilled first like, being logged to the cluster, have context folder ready in workspace and etc. If developer is not logged into cluster it is not even possible to see what we have.
Extension should provide the view where all resources presented as a tree and has context menu/default commands to trigger workflow to use that item to create s2i component with specific version and or a devfile component based on local workspace folder with sources or specific starter project if workspace folder is empty.
For S2I Component Version and Starter Project nodes there should be commands to make it simple to look at the example code we have in git or any kind of source control:
For S2I Component Type Tags, Devfile Component Type and starter project there should be 'New Component' command to create component using that specific component and for devfile components starter project. For s2i components you can first clone sample project into workspace and then use it as context folder when creating component.
The text was updated successfully, but these errors were encountered: