Closed jamesbeedy closed 4 years ago
The caas-base
layer includes a custom WheelhouseTactic
to override the default one built into charm build
to account for the fact that k8s charms cannot perform the normal bootstrap and installation, so instead of bundling packaged wheel or egg files, it has to essentially create an embedded virtualenv. However, both the tactics/
directory and the tactics: []
list in layer.yaml
should be merged without you having to re-specify and include that custom tactic.
That the merging isn't happening as it should is a bug with charm build
. Would you mind moving this issue over to charm-tools?
Trying to create a tactic for my k8s charm and experiencing an issue. The issue is that I cannot build my charm without including the wheelhouse tactic (from layer-caas-base) in my charm.
Building my charm shows (layer.yaml)
Adding the wheelhouse.py tactic to my
tactics/
and to my layer.yaml allows the charm to build.This issue only presents itself when using layer-caas-base in a k8s charm and does not happen when building a legacy charm with layer-basic.
Any ideas?