-
Notifications
You must be signed in to change notification settings - Fork 406
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
CRD documentation list all versions #17421
Conversation
✅ Deploy Preview for kyma-project-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
<!-- TracePipeline v1alpha1 telemetry.kyma-project.io --> | ||
| Parameter | Type | Description | | ||
| ------------------| ---- | --------------------------------------------- | | ||
| **spec.output** | object | Defines a destination for shipping trace data. Only one can be defined per pipeline. | |
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.
Can you remove the "spec." prefix, it is redundant and will reduce the width of the column
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.
sure
Could you ad the "required" flag behind the type so that we have covered all requirements already. That would be great :) |
let me try. but as this tool uses a rather basic way to "parse" openapi it will not be nice |
<!-- Subscription v1alpha1 eventing.kyma-project.io --> | ||
| Parameter | Type | Description | | ||
| ------------------| ---- | --------------------------------------------- | | ||
| **** | object | SubscriptionSpec defines the desired state of Subscription. | |
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.
The "spec" root attribute need to be excluded from generation
| ------------------| ---- | --------------------------------------------- | | ||
| **** | object | Defines the desired state of LogPipeline | | ||
| **files** | Provides file content to be consumed by a LogPipeline configuration | files | |
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.
The description is in second column...
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.
Hi, nice new features :) I have a few suggestions:
- Please remove all parameters' names from the Description to avoid duplication. For example, instead of:
| **backend.emshash** | integer | Emshash defines the hash for the Subscription in EventType. |
write:
| **backend.emshash** | integer | Defines the hash for the Subscription in EventType. |
- For me, the information if something is required doesn't look good in the Type column. How about adding it in parentheses in a new line after the parameter name in the Parameter column? For example:
| **protocolsettings.webhookAuth.tokenUrl** (required) | string | TokenURL defines token URL for OAuth2 |
It should go to a new line under the parameter name, right?
- I added a few suggestions to the descriptions themselves but is there a point of doing that in the autogenerated document? Can I review those in the source files?
|
||
| Parameter | Type | Description | | ||
| ---- | ----------- | ---- | | ||
| **config** | map[string]string | Config defines the configurations that can be applied to the eventing backend. | |
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.
"map[string]string" in the preview displays as "mapstringstring". I guess it should look differently, doesn't it?
| ---- | ----------- | ---- | | ||
| **config** | map[string]string | Config defines the configurations that can be applied to the eventing backend. | | ||
| **id** | string | ID is the unique identifier of Subscription, read-only. | | ||
| **sink** | string **required** | Sink defines endpoint of the subscriber | |
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.
| **sink** | string **required** | Sink defines endpoint of the subscriber | | |
| **sink** | string **required** | Defines the subscriber's endpoint. | |
| **sink** | string **required** | Sink defines endpoint of the subscriber | | ||
| **source** | string **required** | Source Defines the source of the event originated from. | | ||
| **typeMatching** | string | TypeMatching defines the type of matching to be done for the event types. | | ||
| **types** | []string | Types defines the list of event names for the topics we need to subscribe for messages. | |
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.
Is "[ ] string" a string array?
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.
yes it is
| Parameter | Type | Description | | ||
| ---- | ----------- | ---- | | ||
| **config** | map[string]string | Config defines the configurations that can be applied to the eventing backend. | | ||
| **id** | string | ID is the unique identifier of Subscription, read-only. | |
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.
| **id** | string | ID is the unique identifier of Subscription, read-only. | | |
| **id** | string | The unique identifier of the Subscription, read-only. | |
| **config** | map[string]string | Config defines the configurations that can be applied to the eventing backend. | | ||
| **id** | string | ID is the unique identifier of Subscription, read-only. | | ||
| **sink** | string **required** | Sink defines endpoint of the subscriber | | ||
| **source** | string **required** | Source Defines the source of the event originated from. | |
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.
| **source** | string **required** | Source Defines the source of the event originated from. | | |
| **source** | string **required** | The origin from which events are published.| |
| **id** | string | ID is the unique identifier of Subscription, read-only. | | ||
| **sink** | string **required** | Sink defines endpoint of the subscriber | | ||
| **source** | string **required** | Source Defines the source of the event originated from. | | ||
| **typeMatching** | string | TypeMatching defines the type of matching to be done for the event types. | |
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.
| **typeMatching** | string | TypeMatching defines the type of matching to be done for the event types. | | |
| **typeMatching** | string | Defines the matching type for event types. | |
| **sink** | string **required** | Sink defines endpoint of the subscriber | | ||
| **source** | string **required** | Source Defines the source of the event originated from. | | ||
| **typeMatching** | string | TypeMatching defines the type of matching to be done for the event types. | | ||
| **types** | []string | Types defines the list of event names for the topics we need to subscribe for messages. | |
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.
| **types** | []string | Types defines the list of event names for the topics we need to subscribe for messages. | | |
| **types** | []string | Defines the list of event names for the topics we need to subscribe to for messages. | |
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.
In the Description column links don’t display correctly and the formatting is broken (code font, bold, etc.).
|
||
| Parameter | Type | Description | | ||
| ---- | ----------- | ---- | | ||
| **parser** | string | \[Fluent Bit Parsers\]\(https://docs\.fluentbit\.io/manual/pipeline/parsers\)\. The parser specified here has no effect until it is referenced by a \[Pod annotation\]\(https://docs\.fluentbit\.io/manual/pipeline/filters/kubernetes\#kubernetes\-annotations\) on your workload or by a \[Parser Filter\]\(https://docs\.fluentbit\.io/manual/pipeline/filters/parser\) defined in a pipeline's filters section\. | |
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.
Links don't display correctly throughout all the documents.
| **conditions** | array | An array of conditions describing the status of the parser\. | | ||
| **conditions.lastTransitionTime** | string | An array of conditions describing the status of the parser\. | | ||
| **conditions.reason** | string | An array of conditions describing the status of the parser\. | | ||
| **conditions.type** | string | The possible transition types are:\<br\>\- \`Running\`: The parser is ready and usable\.\<br\>\- \`Pending\`: The parser is being activated\. | |
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.
Formatting in the Description column doesn't display correctly throughout all the documents.
they can then be updated with a followup pr
@k15r: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Description
Changes proposed in this pull request:
Related issue(s)