Update field to match argo Workflow spec

maxrjones commented 2 months ago

The example did not work as-is, because the spec field is apiVersion rather than api (ref: https://argo-workflows.readthedocs.io/en/stable/fields/#workflowspec).

Reference Issues or PRs

Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[X] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

[ ] The content is written with plain language (where relevant).
[ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[ ] All links describe where they link to (for example, check the Nebari website).
[ ] This content adheres to the Nebari style guides.

[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
[ ] Don't use flashing GIFs or videos.
[ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

netlify[bot] commented 2 months ago

Name	Link
Latest commit	634fe217d92ad453819b5116c0aec293c0b4be89
Latest deploy log	https://app.netlify.com/sites/nebari-docs/deploys/662c012f0ba69400086e61ae
Deploy Preview	https://deploy-preview-434--nebari-docs.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

viniciusdc commented 2 months ago

Thanks, @maxrjones, for catching it!