Relation terminology inconsistent: "application endpoint" used in two ways
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Tim McNamara | ||
Bug Description
We use the term "application endpoint" in two (mutually incompatible) senses in our documentation.
It's generally used to mean the relation name, e.g. from https:/
> juju add-relation <application>
But our https:/
> Application endpoints can be identified either by:
> <application name>[:<relation name>]
> where application name supplied without relation will be internally expanded to be well-formed
> or
> <model name>.<application name>[:<relation name>]
> where the application is hosted in another model owned by the current user, in the same controller
> or
> <user name>/<model name>.<application name>[:<relation name>]
> where user/model is another model in the same controller
| summary: |
- Relation terminology inconsisten "application endpoint" used in two ways + Relation terminology inconsistent: "application endpoint" used in two + ways |
| Tim McNamara (tim-clicks) wrote | #1 |
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
There's also a third interpretation in our documentation: https:/
> An endpoint (or application endpoint) is used to connect to another application’s endpoint
> in order to form a relation. An endpoint is defined in a charm’s metadata.yaml by the
> collection of three properties: a role, a name, and an interface.