Re: RHEL9 and "ifcfg" network config

        (Nick Anderson had a brief email chat, which was
        accidentally not on this list, but haven't yet come to any
        significant conclusions.)

  The gist of what I said was to map the source data structure to the
  target data structures. Meaning one of:

  - Create a generic data structure, munge the data as necessary for
    `redhat_8' or `redhat_9' so that the keys and values are convenient
    for rendering the file content
  - Model on the structure needed for `redhat_8', munge for `redhat_9'
    so that the keys and values are convenient for rendering the file
    content
  - Model on the structure needed for `redhat_9', munge for `redhat_8'
    so that the keys and values are convenient for rendering the file
    content

  This munging may be achievable directly in policy, or it might make
  sense to hand the source data off to a module and do the necessary
  munging using a higher level language.

  With respect to the INI format, I believe that there still exists an
  issue with respect to being able to select the /last/ section using
  `edit_line' (should have been resolved with
  <https://northerntech.atlassian.net/browse/CFE-452>, but some issue
  remains <https://northerntech.atlassian.net/browse/CFE-3428>,
  <https://northerntech.atlassian.net/browse/CFE-2663>) so that will
  complicate doing partial file management, but if you are managing the
  full file content and know everything you want, then you should be
  able to render the INI via mustache.

-- 
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/87cyyu2b3d.fsf%40northern.tech.