-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] Add a description
field for the provisioners
#269
Labels
enhancement
New feature or request
go
Pull requests that update Go code
good first issue
Good for newcomers
help wanted
Extra attention is needed
Comments
@mathieu-benoit I can give this one a try too |
Oh yes! Please go ahead, and thanks! Much appreciated! |
did a quick iteration before making thing cleaner
|
9 tasks
Json output [
{
"Type": "service-port",
"Class": "(any)",
"Params": [
"port",
"workload"
],
"Outputs": [
"hostname",
"port"
],
"Description": "This expects a workload and port name and will return the hostname and port required to contact it"
},
{
"Type": "volume",
"Class": "(any)",
"Params": [],
"Outputs": [
"source",
"type"
],
"Description": "Creates a volume resource that can be used by other resources in the project\n"
}
] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
go
Pull requests that update Go code
good first issue
Good for newcomers
help wanted
Extra attention is needed
To improve how PEs document their provisioners and expose them to their Devs, it would be better to have a
description
field in the provisioners files.Today, if we add this field in the provisioners files, we get this error:
Rough list of things to do to implement this:
cmdprov.Provisioner
andtemplateprov.Provisioner
and other places where neededscore-compose provisioners list
to display by default this newdescription
fieldThis field should be optional, to avoid any breaking changes with existing/current provisioners.
Note: here is an example of how this could be used: score-spec/community-provisioners#8
The text was updated successfully, but these errors were encountered: