Open polyzos opened 2 years ago
@polyzos I have submitted a PR to fix this doc bug. PTAL, and feel free to let me know. I will fix the rest issues in several follow-up PRs. Thanks.
The configuration options start with an uppercase letter but the reality is they need to pass them with a lowercase start letter.
From a user's perspective its not clear and its hard to understand how they can properly configure their functions/sources/connectors.
Consider the following example we have in the docs
and here is how we describe the configuration options: https://functionmesh.io/docs/functions/function-crd/#function-configurations
Some examples:
Then consider the input/output section on the example above and see our docs here: https://functionmesh.io/docs/functions/function-crd/#input For example the inputs section has typeClassName which is not described in the docs. Or for example in the output section we have the ProducerConf. The users get confused around -> what should i specify there? how to i specify it?
Here you can find some example i had created a few months back: https://github.com/streamnative/streamnative-academy/blob/master/microservices-webinars/deployment/mesh.yaml#L196 as you can see here for example the user can add some ConfigMaps and secrets In the docs: https://github.com/streamnative/streamnative-academy/blob/master/microservices-webinars/deployment/mesh.yaml#L196 we just mention the configuration names, we don't actually educate the user HOW we should specify them for deployment.
All these things cause a lot of confusion and its hard to start using function-mesh for realworld applications.