argoproj / argoproj/argo-workflows
support HTTP template with artifact in body
Open
area/templates/http
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Support artifacts HTTP template bodies
# Use Cases
Send a generated artifact to a rest api via a HTTP template.
```yaml
bodyFrom:
artifact:
name: …
```
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Contributor guide
Research direction
The issue provides no file or test path. Start by locating HTTP template handling and existing artifact support; done means an HTTP template can populate its body from the named artifact and send it to a REST API, with coverage for the YAML shape shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100