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

Component dependencies feature #1372

Open
itowlson opened this issue Aug 28, 2024 · 1 comment · Fixed by #1393
Open

Component dependencies feature #1372

itowlson opened this issue Aug 28, 2024 · 1 comment · Fixed by #1393
Assignees
Labels
spin-3.0 Changes arriving in Spin 3.0

Comments

@itowlson
Copy link
Contributor

In Spin 3, we can satisfy components' imported interfaces by wiring them up in the manifest. The v3 docs will need to cover this. We should consider:

  • Reference documentation
  • Concepts documentation (probably fits into the "writing apps" and/or "building apps" section, or might need a new unit about components as a concept, component registries, etc.)
  • Any caveats around Cloud / SpinKube / registries / etc.
  • Tutorial / example
    • We could have some pre-built demo components and WITs for this in the Fermyon registry (although I am not sure what tooling can use OCI registries right now)
@itowlson itowlson added the spin-3.0 Changes arriving in Spin 3.0 label Aug 28, 2024
@fibonacci1729 fibonacci1729 self-assigned this Sep 10, 2024
@fibonacci1729
Copy link
Contributor

I agree re: adding components as a concept and component registries would be really useful given that source and dependencies both reference "registry" as a concept; however, I'm partial to including that as a followup action item.

@itowlson itowlson linked a pull request Oct 8, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spin-3.0 Changes arriving in Spin 3.0
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants