Merge ~mertkirpici/juju-lint:lp/2009536 into juju-lint:master
Status: | Superseded | ||||||||
---|---|---|---|---|---|---|---|---|---|
Proposed branch: | ~mertkirpici/juju-lint:lp/2009536 | ||||||||
Merge into: | juju-lint:master | ||||||||
Diff against target: |
58 lines (+11/-7) 2 files modified
jujulint/lint.py (+10/-7) tests/functional/requirements.txt (+1/-0) |
||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andrea Ieri | Needs Fixing | ||
Gabriel Cocenza | Needs Fixing | ||
Eric Chen | Needs Fixing | ||
Tianqi Xiao (community) | Approve | ||
🤖 prod-jenkaas-bootstack | continuous-integration | Approve | |
BootStack Reviewers | Pending | ||
Review via email: mp+439819@code.launchpad.net |
This proposal has been superseded by a proposal from 2023-04-05.
Commit message
LP #2009536
Description of the change
lint: check multiple subs for required ones only
Starting with this commit, juju-lint only generates an error in case of
a subordinate charm having multiple units on a given machine if:
- the subordinate charm is declared under the top level "subordinates"
YAML object
- it does not set allow-multiple or sets it to false. this essentially
defines the default value for the "allow-multiple" config as false.
The previous implementation did not care about the subordinate charm
being listed under the "subordinates" at all. This behavior caused a
crash when an optional subordinate is deployed multiple times on a
machine.
This merge proposal is being monitored by mergebot. Change the status to Approved to merge.