Closed ritesh089 closed 2 weeks ago
Transferring issue over to the wadm repository, let me see if I can reproduce here...
I can reproduce with two different versions of the same provider.
/dog-fetcher ➜ cat wadm.yaml|grep http-server
image: ghcr.io/wasmcloud/http-server:0.20.1
/http-hello-world ➜ cat wadm.yaml|grep http-server
image: ghcr.io/wasmcloud/http-server:0.20.0
➜ wash app deploy ./wadm.yaml
Provider ghcr.io/wasmcloud/http-server:0.20.1 is already deployed with a different version in rust-hello-world.
This is an unintended leftover bit of validation.
Affected project(s)
Describe the bug
wash does not allow me to deploy the same provider with a second component that has its own wadm. returns the error :
wash app status for the second component is undeployed .
Note : I did use a different port for the second component , but the same provider.
Steps to reproduce
wash up --wadm-version 0.11.2
wash app deploy wadm.yaml (for component1)
build component 2 : wash build
wash app deploy wadm.yaml (for component 2)
Wadm file : component 1
Wadm (component-2)
Expected behavior
I expect both components to be deployed with the http-server capability provider.
Environment
Screenshots / Logs / Additional context
No response