Re: We are excited to announce the release of Juju 2.2.3!

2017-09-11 Thread Tim Penhey 
We are still getting the docs updated.

https://jujucharms.com/docs/2.2/charms-bundles#setting-charm-configurations-options-in-a-bundle
has a note about the include-file:// and include-base64:// items.

We still seem to be missing details about --bundle-config.

Tim

On 08/09/17 22:41, Sandor Zeestraten wrote:
> Hey Burton, 
> 
> Where can I find the docs on these new bundle options (include-file and
> include-base64) and the --bundle-config option?
> 
> Have a nice weekend
> --
> Sandor Zeestraten
> 
> On Fri, Sep 8, 2017 at 9:43 AM, Burton Swan  > wrote:
> 
> ## New and Improved
> 
> * The remove-machine command has a --keep-instance flag which allows
> the cloud instance to be left running when the machine is removed
> from the Juju model
> 
> * Bundles can now reference local resources by specifying a relative
> path (as can already be done for local charms).
> 
> * Values in local bundles for options and annotations can now
> specify a file to be read for the specified value. This is to
> support charm options where the value is some structured content,
> such as a configuration file. For binary external files, such as
> binary certificates, there is an option to base64 encode the
> contents of the file so it can be used as a string value. The
> referenced file can include the path to the file. The file location
> is relative to the bundle file location. e.g.:
> 
> applications:
> my-app:
> charm: some-charm
> options:
> config: include-file://my-config.yaml
> cert: include-base64://my-cert.crt
> 
> * There is a new option for deploying bundles: --bundle-config. This
> configuration file needs to be a YAML file, and currently only
> supports applications as a top level key. The format of the
> applications is the same as applications section in the bundle. Any
> values specified for an application in the bundle-config file
> override those values defined in the bundle, with the exception of
> the map type values, where the maps are merged with preference given
> to the bundle-config. The purpose of this to allow the use of a
> common bundle definition, and have model specific configuration kept
> in a separate file. Option and annotation values specified in the
> bundle-config file can also use the include-file:// and
> include-base64:// directives mentioned above for local bundles.
> Paths specified are relative to the bundle-config file.
> 
> 
> For a list of all bugs fixed in this release, see
> https://launchpad.net/juju/+milestone/2.2.3
> 
> 
> ## How can I get it?
> 
> The best way to get your hands on this release of Juju is to install
> it as a snap package (see https://snapcraft.io for more info on snaps).
> 
>  snap install juju --classic 
> 
> Other packages are available for a variety of platforms. Please see
> the online documentation at
> https://jujucharms.com/docs/stable/reference-install
> 
> 
> Those subscribed to a snap channel should be automatically upgraded.
> If you’re using the ppa/homebrew, you should see an upgrade available.
> 
> For highlights of this release, please see the documentation at
> https://jujucharms.com/docs/2.2/whats-new
> 
> 
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com 
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> 
> 
> 
> 
> 

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: We are excited to announce the release of Juju 2.2.3!

2017-09-08 Thread Tim Van Steenburgh 
The new bundle stuff is very useful, thanks Juju devs!

On Fri, Sep 8, 2017 at 3:43 AM, Burton Swan 
wrote:

> ## New and Improved
>
> * The remove-machine command has a --keep-instance flag which allows the
> cloud instance to be left running when the machine is removed from the Juju
> model
>
> * Bundles can now reference local resources by specifying a relative path
> (as can already be done for local charms).
>
> * Values in local bundles for options and annotations can now specify a
> file to be read for the specified value. This is to support charm options
> where the value is some structured content, such as a configuration file.
> For binary external files, such as binary certificates, there is an option
> to base64 encode the contents of the file so it can be used as a string
> value. The referenced file can include the path to the file. The file
> location is relative to the bundle file location. e.g.:
>
> applications:
> my-app:
> charm: some-charm
> options:
> config: include-file://my-config.yaml
> cert: include-base64://my-cert.crt
>
> * There is a new option for deploying bundles: --bundle-config. This
> configuration file needs to be a YAML file, and currently only supports
> applications as a top level key. The format of the applications is the same
> as applications section in the bundle. Any values specified for an
> application in the bundle-config file override those values defined in the
> bundle, with the exception of the map type values, where the maps are
> merged with preference given to the bundle-config. The purpose of this to
> allow the use of a common bundle definition, and have model specific
> configuration kept in a separate file. Option and annotation values
> specified in the bundle-config file can also use the include-file:// and
> include-base64:// directives mentioned above for local bundles. Paths
> specified are relative to the bundle-config file.
>
>
> For a list of all bugs fixed in this release, see
> https://launchpad.net/juju/+milestone/2.2.3
>
> ## How can I get it?
>
> The best way to get your hands on this release of Juju is to install it as
> a snap package (see https://snapcraft.io for more info on snaps).
>
>  snap install juju --classic
>
> Other packages are available for a variety of platforms. Please see the
> online documentation at https://jujucharms.com/docs/
> stable/reference-install
>
> Those subscribed to a snap channel should be automatically upgraded. If
> you’re using the ppa/homebrew, you should see an upgrade available.
>
> For highlights of this release, please see the documentation at
> https://jujucharms.com/docs/2.2/whats-new
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: We are excited to announce the release of Juju 2.2.3!

2017-09-08 Thread Sandor Zeestraten 
Hey Burton,

Where can I find the docs on these new bundle options (include-file and
include-base64) and the --bundle-config option?

Have a nice weekend
--
Sandor Zeestraten

On Fri, Sep 8, 2017 at 9:43 AM, Burton Swan 
wrote:

> ## New and Improved
>
> * The remove-machine command has a --keep-instance flag which allows the
> cloud instance to be left running when the machine is removed from the Juju
> model
>
> * Bundles can now reference local resources by specifying a relative path
> (as can already be done for local charms).
>
> * Values in local bundles for options and annotations can now specify a
> file to be read for the specified value. This is to support charm options
> where the value is some structured content, such as a configuration file.
> For binary external files, such as binary certificates, there is an option
> to base64 encode the contents of the file so it can be used as a string
> value. The referenced file can include the path to the file. The file
> location is relative to the bundle file location. e.g.:
>
> applications:
> my-app:
> charm: some-charm
> options:
> config: include-file://my-config.yaml
> cert: include-base64://my-cert.crt
>
> * There is a new option for deploying bundles: --bundle-config. This
> configuration file needs to be a YAML file, and currently only supports
> applications as a top level key. The format of the applications is the same
> as applications section in the bundle. Any values specified for an
> application in the bundle-config file override those values defined in the
> bundle, with the exception of the map type values, where the maps are
> merged with preference given to the bundle-config. The purpose of this to
> allow the use of a common bundle definition, and have model specific
> configuration kept in a separate file. Option and annotation values
> specified in the bundle-config file can also use the include-file:// and
> include-base64:// directives mentioned above for local bundles. Paths
> specified are relative to the bundle-config file.
>
>
> For a list of all bugs fixed in this release, see
> https://launchpad.net/juju/+milestone/2.2.3
>
> ## How can I get it?
>
> The best way to get your hands on this release of Juju is to install it as
> a snap package (see https://snapcraft.io for more info on snaps).
>
>  snap install juju --classic
>
> Other packages are available for a variety of platforms. Please see the
> online documentation at https://jujucharms.com/docs/
> stable/reference-install
>
> Those subscribed to a snap channel should be automatically upgraded. If
> you’re using the ppa/homebrew, you should see an upgrade available.
>
> For highlights of this release, please see the documentation at
> https://jujucharms.com/docs/2.2/whats-new
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

We are excited to announce the release of Juju 2.2.3!

2017-09-08 Thread Burton Swan 
## New and Improved

* The remove-machine command has a --keep-instance flag which allows the
cloud instance to be left running when the machine is removed from the Juju
model

* Bundles can now reference local resources by specifying a relative path
(as can already be done for local charms).

* Values in local bundles for options and annotations can now specify a
file to be read for the specified value. This is to support charm options
where the value is some structured content, such as a configuration file.
For binary external files, such as binary certificates, there is an option
to base64 encode the contents of the file so it can be used as a string
value. The referenced file can include the path to the file. The file
location is relative to the bundle file location. e.g.:

applications:
my-app:
charm: some-charm
options:
config: include-file://my-config.yaml
cert: include-base64://my-cert.crt

* There is a new option for deploying bundles: --bundle-config. This
configuration file needs to be a YAML file, and currently only supports
applications as a top level key. The format of the applications is the same
as applications section in the bundle. Any values specified for an
application in the bundle-config file override those values defined in the
bundle, with the exception of the map type values, where the maps are
merged with preference given to the bundle-config. The purpose of this to
allow the use of a common bundle definition, and have model specific
configuration kept in a separate file. Option and annotation values
specified in the bundle-config file can also use the include-file:// and
include-base64:// directives mentioned above for local bundles. Paths
specified are relative to the bundle-config file.


For a list of all bugs fixed in this release, see
https://launchpad.net/juju/+milestone/2.2.3

## How can I get it?

The best way to get your hands on this release of Juju is to install it as
a snap package (see https://snapcraft.io for more info on snaps).

 snap install juju --classic

Other packages are available for a variety of platforms. Please see the
online documentation at https://jujucharms.com/docs/stable/reference-install

Those subscribed to a snap channel should be automatically upgraded. If
you’re using the ppa/homebrew, you should see an upgrade available.

For highlights of this release, please see the documentation at
https://jujucharms.com/docs/2.2/whats-new
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev