-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve experience of working with freight containing many artifacts #2756
Comments
This is an interesting idea. Need a small bit of clarification. You mentioned "auto-discovery" not working well for this scenario. Did you mean to say you just don't want Freight minted automatically by the Warehouse? Discovery still has to happen for Freight assembly. It's how the artifacts to choose from are found. |
This. Auto-discovery is working, but it may be not desired in cases warehouse produces insane number/all possible combinations of freights and those freights will bloat freight timeline The only possibility I see to normally work with such freights (containing 5-7-10 artifacts) is to rely on existing freight (currently deployed on some stage) as a source of truth with manual freight production |
Yes... I could see how that would be useful. When I sell things on eBay, I actually look first for someone else selling the same thing and click "I have one of these to sell." It clones their listing and I modify accordingly. It's much faster/easier than starting from scratch. You basically want the equivalent of that. 👍 |
Checklist
kargo version
, if applicable.Proposed Feature
Improve dev. experience of working with pipelines where freight may contain many artifacts (5+)
Motivation
Some of applications I have - are legacy services, distributed monoliths, containing large number of different applications, but those applications have a common SDLC and in terms of promotion they're single unit of work, as @krancour says. They need to be promoted across different stages of pipeline at same time therefore they cannot be simply disassembled into separate pipelines or warehouses at the moment
Suggested Implementation
The text was updated successfully, but these errors were encountered: