-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Provisioning template with generated parameters failed through template broker #14445
Comments
Tricky. It looks like the broker received the explicit parameter |
I recognise that at the moment the catalog has no way of specifically detecting fields that will be autogenerated, but it could in principle recognise that these are not required values, as at least this is indicated in the schema. If it were not to send empty values for these fields, might that be the best interim solution? |
It looks like JSON schema can contain extra properties not defined in the spec.
http://json-schema.org/latest/json-schema-core.html If you could annotate the parameters that are generated fields in the schema somehow, we can handle them specially in the UI. This would allows us to add the "generated if empty" placeholder that we have in our current template form as well. |
Also from the spec
|
@jim-minter OK I see your point about required. If the schema doesn't say the property is required, it can be missing from the object entirely and still validate. Brokers should handle that. @jwforres Any objections to leaving out empty, optional values from the instance request? I think we should still look at adding something to indicate that the value will be generated though so we can tell the user. |
I agree that indicating that the value can be generated by the back-end is a nice to have, but there's not a super quick way to implement this because the json schema go library we're using doesn't neatly support adding additional keywords. Also, note that if we start using a new keyword, the chances of it being used by other brokers may be pretty limited. So I think that leaving out empty, optional values is the best first step here. At this point, should this issue go to a trello card @bparees? |
@jim-minter have we already updated the broker to report template parameters that are marked in the template as "generated" and "required" as "optional" in the parameter schema? |
|
(2) is done by openshift/origin-web-catalog#231 |
On Tue, Jun 6, 2017 at 9:48 AM, Ben Parees ***@***.***> wrote:
1. we should report 'required but generatable" parameters as optional.
@jim-minter <https://github.com/jim-minter>'s PR will do that.
2. the web console should not send back optional parameters that have
an empty string value
3. we should open a trello card to annotate "generatable" parameters
so the web console knows they are generatable. Agree that this is something
it might be better to have consensus on across brokers, so maybe open an
issue against the service broker api spec repo first and let's discuss it
there?
Agree we should open the issue to have the discussion, but I suspect the
result will be that there is a recommended convention that is not part of
the spec. That is the status for everything underneath service and plan
metadata and those are arguably more spec worthy than generatable params.
…
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14445 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZk7SFlf4zqTL4Vsv3S2R3UnJo9G-D1ks5sBViQgaJpZM4NtcFd>
.
|
yeah i don't expect this to land in the spec, but if we can get some interested parties to agree on a suitable convention, at least we won't be going it alone. |
issue opened here: openservicebrokerapi/servicebroker#219 |
action items have been resolved or moved to other issues. |
I'm seeing the following error provisioning the template
cakephp-mysql-persistent
through the service catalog.The GitHub secret comes from a generated parameter. It appears the value is not being generated, however.
Here is the
Instance
request the UI is making to the service catalog:Here is the
TemplateInstance
that the broker creates:TemplateInstance YAML
cc @jim-minter @jwforres @bparees
The text was updated successfully, but these errors were encountered: