James Haggerty
James Haggerty
As initially raised in https://stackoverflow.com/questions/56206580/lookahead-inside-or-clause-failing-in-textx/56210085 : The following throws an exception for me (on line 9), complaining that `Expected '.' at position (5, 15) => 'k foo bar *end '.`:...
If you register an object processor, there appears to be no obvious way you can find out the line/column number to report a failure, because this relies on the parser...
#194 and #195 can be useful, but expose the secret in the service instance object. Surprisingly, this is usually ok - most binding outputs are not truly 'secret'. But obviously...
Smith currently checks for conflicts in its own resource names, but allows the user to set the object names in the bundle. Among other things, this means: - two resources...
If we reference into ConfigMaps and Secrets, it can be useful to parse JSON and base 64 decode (so complex configuration can be passed around safely). Lack of json decoding...
Something like :bindsecret in refs could allow looking into bundles inside bundles. This could simplify autowiring in Voyager and make bundle structure clearer? (thought bubble)
Should check against openapi schema: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/util/openapi/openapi.go Make sure crd schemas are exposed here.
If we support #194 and #195, and we want to do #186 and #187, then one option would be to stop supporting plugins as a separate top-level 'thing' and instead...
This is a step in allowing us to change the 'shape' of secrets, which is particularly important due to the way parametersFrom works in Service Catalog: https://github.com/kubernetes-incubator/service-catalog/blob/master/docs/parameters.md (i.e. the secret...
At the moment we don't discover parameter errors until we create ServiceInstance/Binding objects. OSB providers can/should have json schemas for their parameters. However, we can't trivially validate against these if...