make the locks_filename default to db_filename?

[bwitt]

if I'm trying to put a few dconf::db resources into the same db (e.g. local), I have to do something like this

    dconf::db { 'firstone':
      db_dir         => "${dconf::db_base_dir}/local.d",
      db_filename    => '00-firstone',
      locks_filename => '00-firstone',
      settings       => {
        'setting1' => {
          'key1' => 'value1',
        },
      },
      locks          => [
        'key1',
      ],
    }

      dconf::db { 'secondone':
        db_dir         => "${dconf::db_base_dir}/local.d",
        db_filename    => '02-secondone',
        locks_filename => '02-secondone',
        settings       => {
          'setting2' => {
            'key2' => 'value2',
          },
        },
        locks          => [
          'key2',
        ],
      }

Each of these would be in a separate class, and included or not based on a config, so I'd like to keep them separate like this (vs combining into one big dconf::db resource)

maybe we could make the locks_filename default to db_filename instead of 00-default

[jps-help]

Thanks for the suggestion. At first glance this looks like a good/simple enhancement.

Currently we have locks_filename and db_filename independently set to the same value:

  String $db_filename = '00-default',
  String $locks_filename = '00-default',

I'll draft a patch and test when I have some free time.

[jps-help]

I have addressed this in #24 but also took the opportunity to overhaul the whole process of creating multiple keyfiles and locks for a single dconf db.

It's not on the forge yet, but merged into main branch.

The new solution removes the need to define multiple dconf::db resources just to add another keyfile or locks to an existing directory.
You can now create arbitrary keyfiles or locks files using separate resources. Just need to specify a parent directory for each.