Create a PutModelRequest type and change the put endpoint

[thomastaylor312]

After talking with @brooksmtownsend we think that a manifest should always deploy by default when it is put, but this means we need a request body to indicate when we don't want it to deploy immediately. So we'll need to modify the put endpoint to expect a different body

[thomastaylor312]

Note: This should happen either after wadm 0.4 work is done or in wadm 0.5

[brooksmtownsend]

I mostly think this would be nice from an initial perspective, consolidating the put/deploy action into one command which would make it easy for us. Perhaps we could have the deploy body take a manifest instead of a name as an alternative? e.g. wash app deploy -f echo.yaml

Trying to tie this closely to the way that kubectl apply works, which IMO is a great experience for starting out. Oneliner, idempotent, accepts a file or stdin, etc

[thomastaylor312]

I think how we present it as a cli is different from how we structure it as an API. I'm not opposed to adding a shorthand like you suggest, but as an API it might make more sense to keep updating data and deploying said data different parts of the API.

[stale]

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!

[thomastaylor312]

Def not stale