Is there any way to specify multiple storage constraints, e.g. via multiple --storage arguments, at all?
This logic seems a bit different to how network spaces are handled.
For example, network spaces are possible to specify via --constraints [0][1], but there is also the --bind syntax [2] for them which allows space-separated endpoint bindings:
juju deploy --bind "default-space db=db-space db-admin=admin-space" mysql
Since applications may have storage endpoints it seems worthwhile to support something like this for storage.
It seems like a bigger chunk of work than just error handling so I can create a separate bug or discourse topic if needed.
Hi Thomas,
Thank you for looking into it.
Is there any way to specify multiple storage constraints, e.g. via multiple --storage arguments, at all?
This logic seems a bit different to how network spaces are handled.
For example, network spaces are possible to specify via --constraints [0][1], but there is also the --bind syntax [2] for them which allows space-separated endpoint bindings:
juju deploy --bind "default-space db=db-space db-admin= admin-space" mysql
Since applications may have storage endpoints it seems worthwhile to support something like this for storage.
It seems like a bigger chunk of work than just error handling so I can create a separate bug or discourse topic if needed.
[0] https:/ /jaas.ai/ docs/constraint s#heading- -setting- constraints- for-the- initial- controller- and-default- models /jaas.ai/ docs/constraint s-reference /jaas.ai/ docs/deploying- advanced- applications# heading- -deploying- to-network- spaces
[1] https:/
[2] https:/