allow parts of key names called meta and value

[markus2330]

Currently, we simply use "meta" and "value" with special meaning. This makes it impossible to actually use parts of key names with "meta" and "value", which is not so unlikely.

In doc/decisions/semantics_name.md @kodebach proposed to use ®elektra in such cases.

In another case (fuse binding) we used @elektra. So probably we should first review doc/decisions/semantics_name.md if we stay with the decision. (And create an issue that the fuse binding needs to be fixed). Alternatively, we could use @elektra/meta etc. and revise the decision.

[kodebach]

Currently, we simply use "meta" and "value" with special meaning. This makes it impossible to actually use parts of key names with "meta" and "value", which is not so unlikely.

What is this referring to? Sorry, I missed that this is in the ansible repo....

Yes, that is a problem, but I'm not sure "®elektra/meta and ®elektra/value" is the solution. It would be really awkward to use.

First of all, I think this should work:

    - name: set example vegetables
      elektra:
        mountpoint: user:/tests/ansible/vegetables
        keys:
          tomato: ketchup
          potato: fries

Secondly, do we actually translate YAML arrays into Elektra array, i.e. what happens with this:

    - name: set example vegetables
      elektra:
        mountpoint: user:/tests/ansible/vegetables
        keys:
          tomato:
            - ketchup
            - sauce

Because one easy way to fix this would be:

    - name: set example vegetables
      elektra:
        mountpoint: user:/tests/ansible/vegetables
        keys:
          # works as expected, sets values for tomato and potato
          tomato: ketchup
          potato: fries
          # if you need meta and value or values on non-leaf nodes
          fruit:
            apple:
              - value: pie
              - meta:
                  type: string
                  default: juice
            berries:
              - value: bush
              - keys:
                  raspberry: pi
                  blueberry: muffin

We'd need to check that all the objects in the array only contain one key, which must be value, meta or keys and that nothing is repeated, but it would work.

If we do (or want to) translate YAML arrays it could still work, with a bit of fudging:

    - name: set example vegetables
      elektra:
        mountpoint: user:/tests/ansible/vegetables
        keys:
          # works as expected, sets values for tomato and potato
          tomato: ketchup
          potato: fries
          animals:
            - array:
                - species: cow # sets /animals/#0/species = cow
                  name: Bessie # sets /animals/#0/name = Bessie
                - species: dog
                - species: sheep
          # if you need meta and value or values on non-leaf nodes
          fruit:
            apple:
              - value: pie
              - meta:
                  type: string
                  default: juice
            berries:
              - value: bush
              - keys:
                  raspberry: pi
                  blueberry: muffin

[markus2330]

I like the idea.