If you "juju trust" a charm, we allow that charm to ask for the underlying
cloud provider credentials. (the operator is trusting that charm to control
additional resources from the cloud on their behalf).
Other charms don't get credentials, thus you can understand as an operator
that only things you "deploy" will consume resources.
The other bit we've discussed is being able to trust a charm such that they
get credentials to control the Juju model. (allowing them to scale existing
applications, add other applications, etc.) That hasn't been implemented
yet, but is part of the ideas around trust.
On Wed, Oct 16, 2019 at 5:20 AM Tim McNamara <email address hidden>
wrote:
> Public bug reported:
>
> juju help trust provides very little information about what the juju
> trust command does or why it's there. Some questions that would be
> worthwhile pre-emptively address: What is the significance of being
> "trusted"? Are other charms untrustworthy - do they run in some sort of
> sandbox?
>
>
> Usage: juju trust [options] <application name>
>
> Summary:
> Sets the trust status of a deployed application to true.
>
> Global Options:
> [...]
>
> Command Options:
> [...]
> --remove (= false)
> Remove trusted access from a trusted application
>
> Details:
> Sets the trust configuration value to true.
>
> Examples:
> juju trust media-wiki
>
> See also:
> config
>
> ** Affects: juju
> Importance: Medium
> Assignee: Tim McNamara (tim-clicks)
> Status: Triaged
>
>
> ** Tags: cli docs trust
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1848283
>
> Title:
> juju trust has minimal documentation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1848283/+subscriptions
>
If you "juju trust" a charm, we allow that charm to ask for the underlying
cloud provider credentials. (the operator is trusting that charm to control
additional resources from the cloud on their behalf).
Other charms don't get credentials, thus you can understand as an operator
that only things you "deploy" will consume resources.
The other bit we've discussed is being able to trust a charm such that they
get credentials to control the Juju model. (allowing them to scale existing
applications, add other applications, etc.) That hasn't been implemented
yet, but is part of the ideas around trust.
On Wed, Oct 16, 2019 at 5:20 AM Tim McNamara <email address hidden>
wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1848283 /bugs.launchpad .net/juju/ +bug/1848283/ +subscriptions
>
> juju help trust provides very little information about what the juju
> trust command does or why it's there. Some questions that would be
> worthwhile pre-emptively address: What is the significance of being
> "trusted"? Are other charms untrustworthy - do they run in some sort of
> sandbox?
>
>
> Usage: juju trust [options] <application name>
>
> Summary:
> Sets the trust status of a deployed application to true.
>
> Global Options:
> [...]
>
> Command Options:
> [...]
> --remove (= false)
> Remove trusted access from a trusted application
>
> Details:
> Sets the trust configuration value to true.
>
> Examples:
> juju trust media-wiki
>
> See also:
> config
>
> ** Affects: juju
> Importance: Medium
> Assignee: Tim McNamara (tim-clicks)
> Status: Triaged
>
>
> ** Tags: cli docs trust
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju trust has minimal documentation
>
> To manage notifications about this bug go to:
> https:/
>