Proposal for configuring support policy rules

[asakusuma]

Different teams and orgs will have different needs for support policy rules

Teams may want to customize the parameters of a support policy. For instance, a team may want to ignore certain dependencies, i.e. not enforce upgrades for certain dependencies. They may also want different upgrade cadences for specific dependencies. Lastly, in many cases, simply turning on a support policy and expecting consumers to immediately adhere to the policy is untenable (for instance, a major upgrade with a migration may be emminently required shortly after turning on a support policy). There needs to be a way to provide a grace period for onboarding to the support policy, while still providing a warning for when dependencies must be updated.

rendered

[SparshithNR]

where this JSON will reside?
One place I think will be the root of the project being evaluated.
Are we planning to provide CI options to achieve the same?

[asakusuma]

Good question, I don't have a strong opinion here besides ensuring that both the programatic API and CI tool can specify a custom JSON file.

[SparshithNR]

I think we should have both options. Most of the MP will use the JSON file if there are certain deps to be ignored all the time or list is too huge.

[SparshithNR]

If using a config file, you must define a primary policy
We can have a default Policy. Which is

// this is our current default
{
  "primary": {
    "upgradeBudget": {
      "major": 4,
      "minor": 2,
      "patch": 1
    }
  }
}

[asakusuma]

"...or set of custom policies or both. If no primary policy is defined, then the only packages used to calculate policy adherence are the packages specified in the custom polices."

If you define a config file but don't define a primary policy, then we should only look at the dependencies specified in the custom policies.

[asakusuma]

This is for folks who only want their support policy to look at specific dependencies

[SparshithNR]

Do we have a specific reason why we are going with weeks? as all other calculations are qtrs or months

[SparshithNR]

Please check there are two files one with uppercase configuration.md and one lowercase.

[SparshithNR]

We can delete this type def for now.

[SparshithNR]

LGTM