Open bryan-aguilar opened 1 year ago
After doing some digging I find that this is happening because we limit the description length to 200 when generating the manifest. I played around with that value and if we increase it then this description is fixed, but it also adds a lot of extra text to the other descriptions. Turns out, tons of description are being truncated.
@open-telemetry/operator-maintainers how do you feel about increasing our description length?
this is a tough balance to strike. I think @pavolloffay set this as an option recently because the CRD length was overflowing the max bytes. I think we should be showing everything in our API docs, but i don't think we can show everything in the CRD because of the overflow issue.
I am pretty sure the api docs generation depends on the output of make manifests
. The API docs have the same truncation noted here but include the full text when the CRD contains the full text.
🤦 you're right Can we run make api-docs off of non-truncated text? I think that would be an okay balance to strike.
I played around with modifying the api-docs
command to generate the crds in a temporary location but then ran into some problems with Kustomize. I'm not very familiar with these tools, but I am pretty sure it is possible.
Yeah this is def something we should look in to, im not sure what the lift will be. I can dig around a bit today.
It appears that the instrumentation CRD spec.apachehttpd.properties has an incomplete description.
https://github.com/open-telemetry/opentelemetry-operator/blame/3b10d4cc4a64511c900343b13d5048408c592d40/config/crd/bases/opentelemetry.io_instrumentations.yaml#L58