argoproj / argoproj/argo-workflows
Plugin template OpenAPI validation
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Currently, the structure of a plugin template is free-from, it can even be a string:
```yaml
plugin:
hello: "yes"
```
Thats fine. But we could allow plugin developers to define the OpenAPI schema and validate it when the template is created.
# Use Cases
When would you use this?
---
**Message from the maintainers**:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the plugin template creation path and any existing OpenAPI validation support, then clarify where plugin schemas should be defined and what validation errors and successful creation should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100