Update the webex notification provider and markdown

[ahothan]

Signed-off-by: ahothan ahothan@cisco.com

I have tested this against the latest webex API portal and verified I could get notifications in the targeted webex space.
Requires 2 additional parameters to make it work: a room ID and a Webex bot access token (both can be retrieved using the
webex developer web site after registering).
I have also enhanced the formatted markdown.
Example of webex space output:

[kingdonb]

Thank you for this, if you are looking to add an example webex notification provider, the file where provider-specific examples are drawn from is: spec/v1beta1/provider.md

The example would land in the fluxcd docs under here:
https://fluxcd.io/docs/components/notification/provider/#example

(The current supplementary docs from each controller repo are pulled into the fluxcd/website repo on each deploy)

[ahothan]

documentation done

[ahothan]

checking if this markdown format would be better:

<Alert summary in bold>
source: <Kind>/<namespace>/<name>
<message>
| <key>=<value> other kv pairs in manifests (all but summary)

[stefanprodan]

@ahothan can you please post a print screen of how it looks now?

[ahothan]

@stefanprodan
I wanted the summary to be first row as it would show where the notification comes from.
Depending on whether the alerts have a summary or not, the notification will use one or another layout.
The comment for the CreateMarkdown function describes how the markdown looks like based on summary present or not,
Here is a snapshot of a mock up (not real notification so dont pay attention to the exact severity)

In this snapshot, the Alert summary was set to "cc-k8s cluster notification" for the first 2,
thelast 2 is without a summary field.

Please provide any suggestion...

[ahothan]

not sure what to make of this error in the "kind" job:

Run kubectl -n notification-system get providers -oyaml
error: the server doesn't have a resource type "providers"
Error: Process completed with exit code 1.

[stefanprodan]

The e2e tests are filing because your code is not properly formatted, see the first failing step in CI. To fix this, run make fmt then force push the changes.

[stefanprodan]

I wanted the summary to be first row as it would show where the notification comes from.

This would make Webex different from all the others and I'm not for diverging from all the other providers.

[ahothan]

@stefanprodan
Reverted the markdown layout to be similar to others, ran make fmt

[ahothan]

Snapshot from new flux bootstrap with latest version:

[stefanprodan]

LGTM

Thanks @ahothan 🥇