juju deploy --bind is not strict about endpoint names
Bug #1661929 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
| 2.1 |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
For both the bindings declared in a bundle, and for the command line, you are allowed to do:
juju deploy application --bind UNKNOWN=bar
And we will silently ignore the UNKNOWN endpoint, rather than warning/error that you asked us to bind an invalid endpoint.
One result of this is that you can deploy and think you are binding an application to a space, but due to a typo, you are actually not specifying anything.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| assignee: | nobody → John A Meinel (jameinel) |
| status: | Triaged → In Progress |
| description: | updated |
| Changed in juju: | |
| milestone: | 2.1-rc1 → 2.2.0-alpha1 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/