Adds v2 of the index generation script, additions:
New table format:
| Name | Supported Integrations | Tasks | Docs |
eg:
The codebundles directory name will be used by default, and the first word of the dir name is used for the integration default.
The author may override the table name by supplying a Canonical Name metadata value in the robot. eg: Kubernetes Workload Healthcheck in the pic
The author may override the Supported Integrations list by adding the Supports metadata value to the codebundle which contains a CSV list
Names are hyperlinked to the robot file
The full doc string of the codebundle is now used, with a hyperlinked Docs at the end which directs the user to to our RunWhen gitbook frontend
Github action updated to call this instead
uses a yaml config which can have many repos added to it, aggregating many codecollections if we wish in the future
❓ @stewartshea with the Supported Integrations + task names + Docs link I was curious if you still want Use Cases to show up - I felt the new combo is short and sweet but I can add them back in
Adds v2 of the index generation script, additions:
New table format: | Name | Supported Integrations | Tasks | Docs | eg:![image](https://user-images.githubusercontent.com/28266570/231024856-0952a141-27a7-4cc8-a53f-09b0d8d2afc3.png)
The codebundles directory name will be used by default, and the first word of the dir name is used for the integration default.
The author may override the table name by supplying a
Canonical Name
metadata value in the robot. eg: Kubernetes Workload Healthcheck in the picThe author may override the Supported Integrations list by adding the
Supports
metadata value to the codebundle which contains a CSV listNames are hyperlinked to the
robot
fileThe full doc string of the codebundle is now used, with a hyperlinked
Docs
at the end which directs the user to to our RunWhen gitbook frontendGithub action updated to call this instead
uses a yaml config which can have many repos added to it, aggregating many codecollections if we wish in the future
❓ @stewartshea with the Supported Integrations + task names + Docs link I was curious if you still want
Use Cases
to show up - I felt the new combo is short and sweet but I can add them back in