Allow aliases for the rules provided by the snap
Bug #2012952 reported by
Mert Kirpici
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juju Lint |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
The snap package provides some rules files for common configurations, however we still need to provide the full path to them, which I think is not ideal from a user experience point of view.
I propose supporting well documented aliases for the provided defaults.
Instead of this
$ juju-lint -c /snap/juju-
We could have something like this
$ juju-lint -c openstack-focal-ovn ...
Also taking this idea further, a mechanism to declare aliases may be another good feature to have as well.
Changed in juju-lint: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.
Given that it's targeting a built-in ruleset, the reason to run something like
$ juju-lint -c /snap/juju- lint/current/ contrib/ openstack- focal-ovn. yaml
is usually to work around a failed autodetection. So I think it would be more valuable to focus on how to make it less likely for operators to need to run such a command. Is there another use case for wanting to manually pass a built-in ruleset?