Under the contrib folder there are some fixed rules to help users to use juju-lint. Some of then are named like openstack--<ovs|ovn> e.g(openstack-focal-ovn.yaml). To use it the user should pass a command like this:
I think it's very easy to forget to use this "-t openstack" and several checks can be missed if this flag is not passed. I guess it would be good if juju-lint checks if the rule file starts with "openstack" and add the cloud_type automatically.
Logs are necessary to inform the user that the CLI will run using this specific cloud because of the filename.
Under the contrib folder there are some fixed rules to help users to use juju-lint. Some of then are named like openstack--<ovs|ovn> e.g(openstack-focal-ovn.yaml). To use it the user should pass a command like this:
$ juju-lint -c /snap/juju-lint/current/contrib/openstack-focal-ovn.yaml -t openstack /tmp/juju-status-openstack.json
I think it's very easy to forget to use this "-t openstack" and several checks can be missed if this flag is not passed. I guess it would be good if juju-lint checks if the rule file starts with "openstack" and add the cloud_type automatically.
Logs are necessary to inform the user that the CLI will run using this specific cloud because of the filename.
Imported from Launchpad using lp2gh.
date created: 2022-06-27T21:54:45Z
owner: gabrielcocenza
assignee: None
the launchpad url