Closed tmihoc closed 1 year ago
@tmihoc Hi, the machine charm template does not include the config.yaml
file as it is optional. Do you use it?
Hi @syu-w , I think the problem is not so much whether it is generated or not -- the default behavior should, of course, be whatever makes the most sense. The issue is that, when you run charmcraft init --profile machine
, the output says:
Charmed operator package file and directory tree initialised.
Now edit the following package files to provide fundamental charm metadata and other information:
metadata.yaml
config.yaml
...
suggesting that the config.yaml
file is among the files that are generated, whereas it is not. So either we generate that file or we don't mention it here, imo.
The info had updated, and now it is only need to edit charmcraft.yaml
after charmcraft init
. metadata.yaml
and config.yaml
no longer in the default template.
https://github.com/canonical/charmcraft/pull/1149
Bug Description
The
charmcraft init --profile machine
command output says to edit, among other things, theconfig.yaml
file. However, when you inspect the files it has generated, there is noconfig.yaml
file.To Reproduce
charmcraft init --profile machine
.Environment
Charmcraft 2.3.0 on Multipass VM running Ubuntu 22.04
charmcraft.yaml
Relevant log output