argoproj / argoproj/argo-workflows
Configure artifacts using URIs, e.g `s3://my-bucket/my-key`
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
It might be convenient and more compact to represent artifacts by URIs. A bit like [go getter](https://github.com/hashicorp/go-getter), but with the option to put as well as get.
# Use Cases
Add more repositories.
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Contributor guide
Research direction
The issue names no source files, tests, or entry points; start by locating the artifact configuration and repository-handling code, then compare the proposed URI approach with the linked go-getter project. Done would require a decided design that supports adding repositories and getting and putting artifacts through URIs such as s3://my-bucket/my-key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100