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

CLI: wasmer deploy: existing app not detected properly when no namespace specified #4957

Closed
theduke opened this issue Jul 24, 2024 · 0 comments · Fixed by #4965
Closed

CLI: wasmer deploy: existing app not detected properly when no namespace specified #4957

theduke opened this issue Jul 24, 2024 · 0 comments · Fixed by #4965
Assignees
Labels
bug Something isn't working edge-cli

Comments

@theduke
Copy link
Contributor

theduke commented Jul 24, 2024

When running wasmer deploy with the below app config, the command prompts for chosing the owner, even though the app already exists and has an owner. An app id is present in the config.

Correct behaviour: do not prompt for an owner, just detect that the app already exists and deploy.

kind: wasmer.io/App.v0
name: wasmer-tests-js-worker-basic
app_id: da_zRLmILtvUyj2
package: wasmer-tests/js-worker-basic
cli_args:
  - /src/index.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working edge-cli
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants