Add optional params to prototype spec
Fixes #69. Currently we allow users to specify prototypes using Jsonnet. At the head of each prototype should be a comment with semi-structured metadata, e.g., // @apiVersion 0.0.1 // @name io.ksonnet.pkg.nginx-simple // @description Deploys a simple, stateless nginx server with server // blocks (roughly equivalent // to nginx virtual hosts). The nginx container is deployed using a // Kubernetes deployment, and is exposed to a network with a service. // @param namespace string default Namespace in which to put the // application // @param name string Name to give to each of the components Critically, some metadata about params is stored using the `@param` tag, including name, type, and description, for pretty printing. This commit will introduce a new param type, `@optionalParam`. This type has a name, type, default value, and description. It is currently not possible to specify a default value with spaces, but this should be good enough for...
Please register or sign in to comment