What were you trying to do that didn't work?

puppet-openstacklib uses Json.lns of augeas to configure API policies for all RHOSP services. In some cases it leaves policy.json in slightly messy state: contents are valid JSON, but not human-friendly (see example below). Although this problem is cosmetic, some users think that it causes problems because of formatting.

{
    "context_is_admin": "role:admin or role:load-balancer_admin",
    "admin_or_owner": "is_admin:True or project_id:%(project_id)s",

    "load-balancer:read": "rule:admin_or_owner",
    "load-balancer:read-global": "is_admin:True",
    "load-balancer:write": "rule:admin_or_owner",
    "load-balancer:read-quota": "rule:admin_or_owner",
    "load-balancer:read-quota-global": "is_admin:True",
    "load-balancer:write-quota": "is_admin:True"
,
"os_load-balancer_api:loadbalancer:put_failover":"rule:admin_or_owner"} 

Please provide the package NVR for which bug is seen:

ruby-augeas-0.5.0-8.el8ost.1.x86_64
python3-augeas-0.5.0-12.el8.noarch
augeas-libs-1.12.0-6.el8.x86_64

How reproducible:

I have reproduced it using puppet manifests similar to https://github.com/openstack/puppet-openstacklib/blob/stable/train/manifests/policy/base.pp#L48-L64

Expected results

Generated JSON looks like regular ones

Actual results

Json.lns of augeas generates valid JSON, which could be considered invalid from operator's perspective.