After upgrading the wash-cli to v0.27.0, I could not run the echo-messaging component example. With Brooks help, I examined the host's configuration, which revealed that wadm hasn't fully migrated the state from v0.82.0 to v1.0.0.
I should add that addressing the wadm migration issue might or might not address the component deployment issue; so, I leave it out here.
Steps to reproduce
Install wash-cli v0.26.0
Run wash up
Optionally run the http component example
Run wash down
Delete ~/.wash folder to clear history
Upgrade wha-clito v0.27.0
Run wash up
Run nats kv get wadm_state host_default --raw | jq
Expected behaviour
The reported wasmCloud version should be v1.0.0
Additional information
This is what I get by running the nats command mentioned above:
Environment
Describe the bug
After upgrading the wash-cli to v0.27.0, I could not run the echo-messaging component example. With Brooks help, I examined the host's configuration, which revealed that
wadm
hasn't fully migrated the state from v0.82.0 to v1.0.0. I should add that addressing the wadm migration issue might or might not address the component deployment issue; so, I leave it out here.Steps to reproduce
Install
wash-cli v0.26.0
Runwash up
Optionally run the http component example Runwash down
Delete~/.wash
folder to clear history Upgradewha-cli
tov0.27.0
Runwash up
Runnats kv get wadm_state host_default --raw | jq
Expected behaviour
The reported wasmCloud version should be v1.0.0
Additional information
This is what I get by running the nats command mentioned above: