Define a way to test incompatible configurations as code in evergreen

XMLWordPrintable

    • Type: Task
    • Resolution: Won't Do
    • Priority: Minor
    • Component/s: evergreen
    • Evergreen - Milestone 1, Evergreen - Milestone 2

      We need to define how does Evergreen plan to approach the compatibility concerns of the Configuration-as-Code engine.
      Currently, it does not guarantee YAML compatibility when switching between LTS baselines
      E.g. 2.60.x config for agents will fail to load in 2.73+
      If Evergreen plans to let users set their configs for Essentials, then the instance may go south once Essentials picks a new baseline.

            Assignee:
            Unassigned
            Reporter:
            Raul Arabaolaza
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: