Improve approach to valid cases where some data is empty from charmhub
Bug #2020191 reported by
Heather Lanigan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Rather than guard against potential bad data when we unmarshal charmhub responses, solve the problem where the data is received.
Example core/charm/
// NOTE: Charmhub returns a "{}\n" when no config.yaml exists for
// the charm, e.g. postgreql. However, this will fail the charm
// config validation which happens in ReadConfig. Valid config
// are nil and "Options: {}"
if configYAML != "" || strings.
chConfig, err = charm.ReadConfi
if err != nil {
return corecharm.
}
}
Changed in juju: | |
milestone: | 2.9.44 → 2.9.45 |
Changed in juju: | |
milestone: | 2.9.45 → 2.9.46 |
To post a comment you must log in.