payloads validation against charm declarations
Bug #1698970 reported by
Anastasia
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
Currently, payloads are validated against charm declaration in the wrong places and in the wrong way.
For example, payload hook commands read metadata.yaml on unit's machine directly. This also means that this type of validation is missing in the most central area - just before payloads information is persisted in the database.
Validation needs to be moved to state layer to ensure that it is using central unit.charm() logic to access charm metadata.
| Changed in juju: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Anastasia (anastasia-macmood) |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
| Changed in juju: | |
| milestone: | 2.3-alpha1 → none |
| Changed in juju: | |
| assignee: | Anastasia (anastasia-macmood) → nobody |
| status: | In Progress → Triaged |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
PR against develop (2.3): https:/