Implement Error Bingo mapping for nextsteps generation

[jon-funk]

• Adds a troubleshooting lookup keyword that can "suggest" nextsteps based on a error bingo board, called RW.NextSteps.Suggest
• Adds RW.NextSteps.Format keyword to allow for quick injection of live object values/names into nextsteps message before issue submission to reduce robot bloat
• Board is based on a maintained static yaml mapping file, specific to each system/platform (eg: 1 for Kubernetes, 1 for ECS, 1 for Google Cloudrun, etc)
• Adds RW.CLI.Run Bash File keyword

See https://github.com/runwhen-contrib/rw-cli-codecollection/blob/err-bingo/codebundles/cmd-test/runbook.robot for samples

[jon-funk]

Example walkthrough of troubleshooting a postgres issue based on API logs:

• using kubectl get logs in a previous line, a author could get OperationalError: FATAL: connection limit exceeded from their API logs
• They then provide this to the Suggest keyword like so:

    ${next_steps}=    RW.NextSteps.Suggest    OperationalError: FATAL: connection limit exceeded for non-superusers

• This performs a lookup in the troubleshooting mapping for Kubernetes, using a fuzzy match (levenshtein distance) this will match to https://github.com/runwhen-contrib/rw-cli-codecollection/blob/err-bingo/libraries/RW/NextSteps/Kubernetes/mapping.yaml#L44 which is an alias for https://github.com/runwhen-contrib/rw-cli-codecollection/blob/err-bingo/libraries/RW/NextSteps/Kubernetes/mapping.yaml#L33 producing those tasks+object entries

The produce next step will be organized to the following string:

Get Standard Postgres Resource Information, Describe Postgres Custom Resources, Get Postgres Pod Logs & Events, Get Postgres Pod Resource Utilization, Get Running Postgres Configuration, Get Patroni Output, Run DB Debug Queries


StatefulSet:$postgres_name

• Either referencing codebundle configuration or pulling the object name with a CLI command, we can inject the database name into the above message like so:

    ${next_steps}=    RW.NextSteps.Format    ${next_steps}
    ...    postgres_name=${db_name.stdout}

The ${next_steps} string now adheres to the format requested by the platform team and is ready for submission in an issue.

This should:

• reduce robot code bloat and repeated string format calls
• leaves the next_steps formatting up to a keyword which we can update to match the platform's needs if needed in the future
• allows platform troubleshooting experts to update mappings over time while other authors simply pull from the mapping with error messages
• multiple mappings can be intertwined so troubleshooting next_steps can be generated for up the stack or down the stack relative to the current error being investigated

[stewartshea]

Love it, excited to try it and see how it fits into my current flow.