Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match the schema in the publishing cluster #84

Conversation

angelraynovft
Copy link
Contributor

@angelraynovft angelraynovft commented Oct 4, 2024

Description

After the deployment of the annotations synchronization between PAC and Publishing cluster. We were sending PAC requests that does not validate with the annotation schemas in the publishing cluster causing errors.

What

We are introducing an annotations body struct which helps us match the schema in the publishing cluster. This way we can filter the required fields and avoid validation errors.

Why

https://financialtimes.atlassian.net/browse/UPPSF-5624

Anything, in particular, you'd like to highlight to reviewers

Changes can be tested on Staging

Scope and particulars of this PR (Please tick all that apply)

  • Tech hygiene (dependency updating & other tech debt)
  • Bug fix
  • Feature
  • Documentation
  • Breaking change
  • Minor change (e.g. fixing a typo, adding config)

DoD - Ensure all relevant tasks are completed before marking this PR as "Ready for review"

  • Test coverage is not significantly decreased
  • All PR checks have passed
  • Changes are deployed on dev before asking for review
  • Documentations remains up-to-date
    • OpenAPI definition file is updated
    • README file is updated
    • Documentation is updated in upp-docs and upp-public-docs
    • Architecture diagrams are updated

This Pull Request follows the rules described in our Pull Requests Guide

We are introducing an annotations body struct which helps us
match the schema in the publishing cluster. This way we can filter the required fields and avoid validation errors.
@angelraynovft angelraynovft requested a review from a team as a code owner October 4, 2024 11:53
Copy link

@agrancharova agrancharova left a comment

Choose a reason for hiding this comment

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

LGTM!

@agrancharova agrancharova requested a review from a team October 7, 2024 06:40
@angelraynovft angelraynovft merged commit 67a5a2d into master Oct 7, 2024
2 checks passed
@angelraynovft angelraynovft deleted the fix/UPPSF-5624-validate-annotations-schema-in-pac-before-sending-to-publish branch October 8, 2024 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants