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
Allow dependencies to be defined on params #70
Conversation
|
I have read through the attached issue and I like the solution that you guys came up with. Since this will involve an addition to the Bundle spec this type of change will require a version bump of the Bundle Spec along with documentation updates (see here for current documentation around Bundle spec). |
|
From discussing at the community meeting we agreed that this will require a minor version bump of the Bundle spec bringing us to version |
| Updatable bool `json:"updatable"` | ||
| DisplayType string `json:"displayType,omitempty" yaml:"display_type,omitempty"` | ||
| DisplayGroup string `json:"displayGroup,omitempty" yaml:"display_group,omitempty"` | ||
| Dependencies []Dependency `json:"dependencies,omitempty" yaml:"dependencies,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can only handle a single dependency here currently in the broker due to limitations in the frontend lib but I think to future proof where we may be able to do this if we can extend that lib, leaving this as a slice makes sense IMO. What do people think?
The spec itself should be able to support multiple dependencies if my understanding of it is correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed @philipgough allow multiple dependencies.
|
Thanks for doing a doc PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm actually okay with this, I don't see any issues.
| @@ -1,3 +1,6 @@ | |||
| vendor* | |||
| coverage-all.out | |||
| coverage.out | |||
|
|
|||
| # IDE baggage | |||
| .idea/ | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is acceptable
| Updatable bool `json:"updatable"` | ||
| DisplayType string `json:"displayType,omitempty" yaml:"display_type,omitempty"` | ||
| DisplayGroup string `json:"displayGroup,omitempty" yaml:"display_group,omitempty"` | ||
| Dependencies []Dependency `json:"dependencies,omitempty" yaml:"dependencies,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed @philipgough allow multiple dependencies.
Relates to openshift/ansible-service-broker#859