Skip to content
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

MetaPackage capability #1434

Closed
alexbarbato opened this issue Jan 4, 2024 · 5 comments
Closed

MetaPackage capability #1434

alexbarbato opened this issue Jan 4, 2024 · 5 comments
Labels
discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@alexbarbato
Copy link

Describe the problem/challenge you have
Currently we install a number of Packages - they have interdependencies, but there is currently no codified way to formalize those interdependencies.

Describe the solution you'd like
Ideally there'd be some API that allows me codify a series of Packages go together. In theory you could do that with a Package, but absent the tooling supporting it becomes a bit of a bridge too far for the average user.

In order to seamlessly do that you have to much of the plumbing to pass around values to children packages as an example.


Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@alexbarbato alexbarbato added carvel-triage This issue has not yet been reviewed for validity enhancement This issue is a feature request labels Jan 4, 2024
@renuy renuy added discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed carvel-triage This issue has not yet been reviewed for validity labels Jan 9, 2024
@praveenrewar
Copy link
Member

@alexbarbato Do you think solving the problems mentioned in #361 would work for your use case?

@alexbarbato
Copy link
Author

Oo that does cover the use cases I described! Is there a plan to pick up any of that work?

I guess we can close this one then?

@praveenrewar
Copy link
Member

We haven't prioritised it yet, however there has been demand from the community for it and we are trying to look more into how we can best solve the dependency management problem. I am okay with keeping this issue open till we have an update.

@Sarita-Singh
Copy link

Sarita-Singh commented Jan 15, 2024

Hey @praveenrewar I think if there is bazel support for the project, we can get package dependencies including transitive dependencies through bazel query

@renuy
Copy link

renuy commented Mar 5, 2024

Closing this, as we are working on dependency management.
carvel-dev/carvel#732

@renuy renuy closed this as completed Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Archived in project
Development

No branches or pull requests

4 participants