Re: mergedata, etc.: what happens with duplicate keys?
"'Vratislav Podzimek' via help-cfengine" <[email protected]>
| Newsgroups | gmane.comp.sysutils.cfengine.general |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2021-08-05 at 03:19 -0700, [email protected] wrote: > Thanks, Bas. I'll take a look. > > It seems that this behaviour ("last one wins") ought to be documented, so that we, the users, know > what to expect, and that it is intentionally designed to behave this way. > > Documenting it would also means that the behaviour should be preserved into the future. > > Without such CFE documentation, it would be possible for a future implementation simply to change > the behaviour. and for such a change to be called a "feature". By adding documentation into CFE, it > would means that any such change would be reasonably classified as a "bug" (or that such change > would have earlier been planned, announced, managed, etc.). > > I'd really like to see CFE themselves document and confirm this "last one wins" behaviour. Could you please create a ticket at https://tracker.mender.io/secure/CreateIssue.jspa ? Thanks! -- Vratislav > > -- David Lee > On Monday, 2 August 2021 at 22:45:02 UTC+1 Bas van der Vlies wrote: > > David, > > > > the cf_surfsara_lib also depends a lot of mergdate. The last one wins, see for a small example: > > * https://github.com/basvandervlies/cf_surfsara_lib#mustachejson-rules > > > > > > regards > > > > > On 31 Jul 2021, at 13:43, [email protected] <[email protected]> wrote: > > > > > > All the documentation and examples about "mergedata" (and bundle "cmerge", etc.) seem to be > > based on non-overlapping data sets. For example, with two simple key:value JSON datasets, the > > examples and documentation have no overlap of keys. > > > > > > But what is supposed to happen when the same key, and with potentially different value, appears > > in both JSON datasets? > > > > > > My proposed use-case is two simple JSON key:value datasets. The first can be regarded as a full > > and complete set of default key:value pairs; the second is smaller and contains override values > > for a subset of those same keys. The desired result would be that full set as modified by the > > overrides. > > > > > > There seems to be no documentation describing how this is handled, not even whether it is > > regarded as an error condition. If it is documented somewhere, it seems well hidden. > > > > > > If I should be using something else rather than "mergedata", let me know. > > > > > > Any thoughts? Primarily about my proposed use-case, but also about improving the documentation > > (e.g. at function "mergedata") to describe this case of same-key merging. > > > > > > Assume CFE 3.12, but if CFE 3.15 would be different, that would be possible. (By the way my > > reading of documentation also included some 3.18.) > > > > > > -- David Lee > > > > > > > > > -- > > > You received this message because you are subscribed to the Google Groups "help-cfengine" group. > > > To unsubscribe from this group and stop receiving emails from it, send an email to > > [email protected]. > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/help-cfengine/a4a3e96b-4cf5-4e5d-b531-f1504cb18333n%40googlegroups.com > > . > > > -- > You received this message because you are subscribed to the Google Groups "help-cfengine" group. > To unsubscribe from this group and stop receiving emails from it, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/help-cfengine/a93f63ad-f03f-47c1-b324-b5c970c3f3d9n%40googlegroups.com > . -- You received this message because you are subscribed to the Google Groups "help-cfengine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/3c21b44e5892bdcd1359eab198d6c022d8f0b33a.camel%40northern.tech.
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEENAH7ns+FyuCe6j1XmyV2peQQR/QFAmEaaogACgkQmyV2peQQ R/RDlA//cz6ycs+fhRi0djn5UGbR3pnYKGC7x6GwYj6JTtNgH98gfAvzdcYyMdxh JSkHBVtBC8rHGm2K9v77u0pojX54bZe/qKhHNZvoupN8wMfXsM59GeZ7u6smW67Y YuuPzXmdcxnM+a99PE54UhWrjaxbQoxmcxJjwYFptiQSnDiqQx+b3aN+6gBr07J6 GfUcYWj2fwHzYvNfceKImNMksgQ+EKuMs0TXbjVsSB23RrWG6ZZU0bljO94dsmOt GhvNvXcOI9D0i+BSMThEq+iujPM+WotLPNkQ2scdFmlPhnrB54njaJ+Abt4OPL1F 8Ja0riJKoa8FXDIyncZC3vY+gyx2lZ+Gh36sZsQ8YkbpMXPJyMQX5KCd6UjiPP+O edVVPg/DItMhNBxw+e3uFw51SxY4L4TowHl+PZ4hWRpASnnI4aNTfepD0MBiQyx0 LvCH1KmlK5ZWPPZkSt5ru/TmmbsF4GzGGQq9e08yaeEuPiXD2t9x2Ilhmolw4Rbo 9rQRzkhVWpAg3WPaMl06WfoEi+384ajVKdUwVcT4rQqhJwg1Nd0XmorJL2c7uU3w BHJcRWLxCHn2S1aKomiUg7350p8AlJxYiAs0ovdmR3sHxTekl+QgdeS7zqBUfxhj RaHIYuErw/LN2bfzkw+sDymlUr02V1h5drHAeg8yT7yEZkH4myg= =3AMG -----END PGP SIGNATURE-----