You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1182 and #2524 are part of enabling pushing and pulling components to/from registries.
With #2524 in Spin 2.6.0, there is a gap in how a sinlge component, can be pushed to a registry. If e.g., you create a WASI-HTTP incoming-handler, and want to push it to a registry, you hvae to use a tool like Oras.
The workflow works, using spin registry push today, but you can only do that if a spin.toml file is present in the diretory from which you push the component.
I'd like to prospoe adding an option to push a component using spin registry push - e.g., spin registry push component ttl.sh/my/name:0.0.1 -f my_component.wasm, to make this workflow easier.
The text was updated successfully, but these errors were encountered:
#1182 and #2524 are part of enabling pushing and pulling components to/from registries.
With #2524 in Spin 2.6.0, there is a gap in how a sinlge component, can be pushed to a registry. If e.g., you create a WASI-HTTP incoming-handler, and want to push it to a registry, you hvae to use a tool like Oras.
The workflow works, using
spin registry push
today, but you can only do that if aspin.toml
file is present in the diretory from which you push the component.I'd like to prospoe adding an option to push a component using
spin registry push
- e.g.,spin registry push component ttl.sh/my/name:0.0.1 -f my_component.wasm
, to make this workflow easier.The text was updated successfully, but these errors were encountered: