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

The wasmer package tag command should not need a manifest #4672

Open
xdoardo opened this issue May 13, 2024 — with Linear · 0 comments
Open

The wasmer package tag command should not need a manifest #4672

xdoardo opened this issue May 13, 2024 — with Linear · 0 comments
Assignees
Labels
🎉 enhancement New feature! 📦 lib-cli About wasmer-cli priority-high High priority issue stretch

Comments

Copy link
Contributor

xdoardo commented May 13, 2024

Right now the wasmer package tag command requires the package's manifest to be specified in some way, either explicitly giving its path or having it in the current working directory.

We should use the manifest only as a fallback in case the user did not provide every information necessary: as an idea, we could have the command in the format

wasmer package tag sha256:abcd...... namespace/name --version 0.1.0

with the second positional argument (namespace/name) being optional and filled in from the manifest if present, and the same for the version.

@xdoardo xdoardo added 🎉 enhancement New feature! 📦 lib-cli About wasmer-cli labels May 13, 2024 — with Linear
@xdoardo xdoardo self-assigned this May 13, 2024
@syrusakbary syrusakbary added the priority-high High priority issue label May 14, 2024
@xdoardo xdoardo added the stretch label May 14, 2024 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 enhancement New feature! 📦 lib-cli About wasmer-cli priority-high High priority issue stretch
Projects
None yet
Development

No branches or pull requests

2 participants