Skip to content

Corrected version and See also link in MPF evaluation_order docs#3197

Open
nickanderson wants to merge 1 commit into
cfengine:masterfrom
nickanderson:ENT-13495-doc-fixes/master
Open

Corrected version and See also link in MPF evaluation_order docs#3197
nickanderson wants to merge 1 commit into
cfengine:masterfrom
nickanderson:ENT-13495-doc-fixes/master

Conversation

@nickanderson

Copy link
Copy Markdown
Member

What

Follow-up doc corrections to #3192 (body common control evaluation_order
via augments), both in MPF.md:

  1. Version. #3192 documented control_common_evaluation_order and the
    "cf-agent inherits from body common control" note as 3.28.0. That merged
    to master, which is 3.29.0 (.CFVERSION); 3.28.0 is already tagged.
    Corrected both to 3.29.0.
  2. Cross-reference. The new section's "See also" linked evaluation_order
    in body common control
    to [cf-agent#evaluation_order] (the agent
    control anchor). Corrected to [Components#evaluation_order], matching the
    convention already used on the reference pages.

Why

MPF.md is included verbatim into docs.cfengine.com
(reference/masterfiles-policy-framework/), so both errors would publish as-is:
a wrong "Introduced in" version and a See-also link that lands on the wrong body.

Ticket: ENT-13495

Follow-up to "Made evaluation_order in body common control configurable
via Augments" (cfengine#3192).

- control_common_evaluation_order, and the note that cf-agent inherits the
  evaluation order from body common control, ship in 3.29.0 (current
  master) rather than 3.28.0, which is already released.
- The "See also" for evaluation_order in body common control pointed to
  the body agent control anchor ([cf-agent#evaluation_order]); corrected
  to [Components#evaluation_order].

Ticket: ENT-13495
Changelog: None
@nickanderson

Copy link
Copy Markdown
Member Author

@cf-bottom jenkins please

@cf-bottom

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants