Relation terminology inconsistent: "application endpoint" used in two ways

Bug #1884182 reported by Tim McNamara
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
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

> juju add-relation <application>[:<application endpoint>] <offer url>[:<offer endpoint>]

But our

> 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
Revision history for this message
Tim McNamara (tim-clicks) wrote :

There's also a third interpretation in our documentation:

> 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.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.