juju deploy --config option ignored when deploying a bundle

[Casey Marshall]

When I deploy bundles, the --config option does not seem to work.

Steps to reproduce:

bundle.yaml:
---
series: trusty
services:
  wordpress:
    charm: "cs:trusty/wordpress-4"
    expose: True
    num_units: 1
  mysql:
    charm: "cs:trusty/mysql-33"
    num_units: 1
relations:
  - - "wordpress"
    - "mysql"

config.yaml:
---
mysql:
  flavor: percona

$ juju deploy --config config.yaml bundle.yaml
added charm cs:trusty/mysql-33
service mysql deployed (charm: cs:trusty/mysql-33)
added charm cs:trusty/wordpress-4
service wordpress deployed (charm: cs:trusty/wordpress-4)
service wordpress exposed
related wordpress and mysql
added mysql/0 unit to new machine
added wordpress/0 unit to new machine
deployment of bundle "bundle.yaml" completed
$ juju get mysql
...
  flavor:
    default: true
    description: Possible values are 'distro' or 'percona'
    type: string
    value: distro
...

This is with a recent master, 2.0-alpha1-trusty-amd64 (fc73776d8094f415d479dd2fc54d5f16ed6694e6)

[Cheryl Jennings (cherylj)]

Just tried this on master, and now --config is not allowed when deploying bundles:

$ juju deploy /tmp/bundle.yaml --config /tmp/config.yaml
ERROR Flags provided but not supported when deploying a bundle: --config.