GoogleContainerTools / GoogleContainerTools/skaffold
Extend skaffold init --analyze api to also list the supported deployers in a workspace
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
Currently, "skaffold init --analyze" api returns the list of supported builders in a workspace.
Can 'skaffold init --analyze' api be extended to also return the list of supported deployers in a workspace?
Along with above, can 'skaffold init' api be extended to take a supported deployer along with a supported builder to generate the skaffold.yaml file?
IDEs can leverage this info to
1. Provide more visibility to users on the deployer and the corresponding deployment manifests being used to run/debug the app.
- For example, for kubernetes deployer, we would also like to get the list of kubernetes manifests in the workspace.
- User can then select the set of manifests they are interested to use for the deployment.
- Similarly for kustomize, helm etc.
2. Provide a choice to the user on the deployer they would like to use.
- Users will be shown the available deployers (say kubernetes, kustomize etc) in the workspace.
- Users can choose the one they like.
- IDEs use 'skaffold init' api to generate the corresponding skaffold.yaml file with the specified builder and deployer.
Contributor guide
Assessment
This issue has not been assessed yet.