Skip to content

Conversation

@rashmigottipati
Copy link
Contributor

What this PR does / why we need it:

This PR adds change validation to the CRD Upgrade Safety preflight check to prevent changes to the following field constraints during a CRD upgrade operation:

  • maximum
  • maxLength
  • maxItems
  • maxProperties

Which issue(s) this PR fixes:

#914

Does this PR introduce a user-facing change?

Add change validation to the CRDUpgradeSafety pre-flight check that field constraints such as maximum, maxLength, maxItems and maxProperties are not added or decreased during a CRD upgrade

Additional Notes for your reviewer:

Review Checklist:
  • Follows the developer guidelines
  • Relevant tests are added or updated
  • Relevant docs in this repo added or updated
  • Relevant carvel.dev docs added or updated in a separate PR and there's
    a link to that PR
  • Code is at least as readable and maintainable as it was before this
    change

Additional documentation e.g., Proposal, usage docs, etc.:


@rashmigottipati
Copy link
Contributor Author

cc @everettraven

…reflight check

Signed-off-by: Rashmi Gottipati <chowdary.grashmi@gmail.com>
@rashmigottipati rashmigottipati force-pushed the feature/add-maximums-validation-check branch from 0acdf73 to 14379d8 Compare May 7, 2024 14:14
@rashmigottipati
Copy link
Contributor Author

Rebased and squashed commits.

Copy link
Member

@praveenrewar praveenrewar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

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

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants