Public bug reported: When using an intermediate layer (nodejs) to install an extra apt repository, I've run into an issue where the default config.yaml options from the intermediate layer are not being rendered into the final built charm.
Specifically, I'm using the nodejs charm here: https://github.com/battlemidget/juju-layer-node I'd like to *not* specify the 'install_sources' and 'install_keys' options in my top level config.yaml, since the layer has those values set to sane defaults. However, if I leave those unset, the built charm ends up using the nodejs' underlying apt layer's config.yaml defaults. My charm is available here: https://code.launchpad.net/~jamon/+junk/hubot When I do a git checkout and charm build of the nodejs charm on its own, I get a rendered config.yaml that looks like this, which is what I would expect. Note hose the install_sources and keys are set properly. "options": "extra_packages": "description": "Space separated list of extra deb packages to install.\n" "type": "string" "default": "" "package_status": "default": "install" "type": "string" "description": "The status of service-affecting packages will be set to this value\ \ in the dpkg database. Valid values are \"install\" and \"hold\".\n" "install_sources": "description": "List of extra apt sources, per charm-helpers standard format (a\ \ yaml list of strings encoded as a string). Each source may be either a line\ \ that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name>\ \ for adding Personal Package Archives, or a distribution component to enable.\n" "type": "string" "default": | - "https://deb.nodesource.com/node_4.x main" "install_keys": "description": "List of signing keys for install_sources package sources, per\ \ charmhelpers standard format (a yaml list of strings encoded as a string).\ \ The keys should be the full ASCII armoured GPG public keys. While GPG key\ \ ids are also supported and looked up on a keyserver, operators should be aware\ \ that this mechanism is insecure. null can be used if a standard package signing\ \ key is used that will already be installed on the machine, and for PPA sources\ \ where the package signing key is securely retrieved from Launchpad.\n" "type": "string" "default": | - '68576280' Is this behaviour to be expected, and I'll just have to live with setting options for n intermediate layers in my top-level config.yaml? Or is there something I'm missing, or is there a bug in one of the relevant charms? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: charm 2.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 23 14:57:46 2016 SourcePackage: charm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: charm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616095 Title: charm build does not expose default config options from intermediate layers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1616095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
