[BUG] Using --wasmcloud-start-only with wash up does not find locally installed versions
vados-cosmonic opened this issue · comments
Describe the bug
When trying to test a local wasmcloud-otp
version, wash up --wasmcloud-version <local version>
does not find versions that have been installed to ~/.wash/downloads
when --wasmcloud-start-only
is used.
The related code seems to indicate that using the flag causes a failure to always occur.
To Reproduce
Steps to reproduce the behavior:
- Build a custom version of
wasmcloud-otp
(i.e. runmake release
inwasmcloud-otp/wasmcloud_host
- Install the custom version to
~/.wash/downloads
(ex.~/.wash/downloads/v0.63.0
) - Attempt to run
wash up --wasmcloud-version <local version> --wasmcloud-start-only
Expected behavior
wash up
should recognize the custom version that has been added to ~/.wash/downloads
, with --wasmcloud-start-only
specified.
Screenshots
N/A
**Environment (please complete the following information) **
- OS: Linux
- Shell: Bash
wash
Versionv0.16.2
Additional context
N/A
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!
Unmarked as stale. This one is still an issue 🙏