argoproj / argoproj/argo-workflows
SQL artifacts
Open
area/artifacts
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
It would probably be neat to be able to have:
* Input artifacts based on an SQL query.
* Output artifacts written to a database.
# Use Cases
When would you use this?
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Contributor guide
Research direction
No files, tests, or entry points are named in the issue. Start by locating existing input and output artifact handling and the project's database integrations; done would require a defined approach for SQL-query inputs and database-backed outputs, with scope and validation identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100