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

fix(ESSNTL-5612): Update Staleness & Deletion Keys + Route Protection #2114

Merged
merged 4 commits into from
Dec 13, 2023

Conversation

adonispuente
Copy link
Contributor

@adonispuente adonispuente commented Dec 4, 2023

There should be no functionality changes frontend wise with this PR. The backend is changing the api keys so the frontend needs to be updated.

This also protects the route via feature flag.
This cannot be merged until RedHatInsights/insights-host-inventory#1573 is merged

New keys with merged PR:
conventional_time_to_stale
"conventional_time_to_stale_warning": "",
"conventional_time_to_delete": "",
"immutable_time_to_stale": "",
"immutable_time_to_stale_warning": "",
"immutable_time_to_delete"

@adonispuente adonispuente changed the title Staleness keys fix(ESSNTL-5612): Update Staleness & Deletion Keys + Route Protection Dec 4, 2023
@codecov-commenter
Copy link

codecov-commenter commented Dec 4, 2023

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (5871f3a) 57.62% compared to head (f64e039) 57.51%.

Files Patch % Lines
src/Routes.js 66.66% 1 Missing ⚠️
src/components/InventoryHostStaleness/constants.js 98.73% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2114      +/-   ##
==========================================
- Coverage   57.62%   57.51%   -0.11%     
==========================================
  Files         193      193              
  Lines        6192     6195       +3     
  Branches     1713     1715       +2     
==========================================
- Hits         3568     3563       -5     
- Misses       2624     2632       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@adonispuente adonispuente marked this pull request as ready for review December 7, 2023 19:50
@adonispuente adonispuente requested a review from a team as a code owner December 7, 2023 19:50
@adonispuente adonispuente requested a review from gkarat December 7, 2023 19:53
@mkholjuraev
Copy link
Contributor

/retest

Copy link
Contributor

@mkholjuraev mkholjuraev left a comment

Choose a reason for hiding this comment

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

While testing locally, I encountered this error:

{ "detail": "Validation Error: {'conventional_time_to_deletion': ['Unknown field.']}", "status": 400, "title": "Bad Request", "type": "about:blank" }

@adonispuente
Copy link
Contributor Author

@mkholjuraev Sorry about that, The ticket wasnt up to date and I was using an old schema, Ive updated the PR so that its uses the api keys that are now merged into BE stage

@adonispuente
Copy link
Contributor Author

/retest

Copy link
Contributor

@mkholjuraev mkholjuraev left a comment

Choose a reason for hiding this comment

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

LGTM! everyting works as described. Let's make the commit lint happy and then merge

@adonispuente
Copy link
Contributor Author

/retest

3 similar comments
@adonispuente
Copy link
Contributor Author

/retest

@gkarat
Copy link
Contributor

gkarat commented Dec 13, 2023

/retest

@computercamplove
Copy link
Contributor

/retest

@adonispuente adonispuente merged commit aff72b5 into RedHatInsights:master Dec 13, 2023
2 checks passed
@gkarat
Copy link
Contributor

gkarat commented Dec 13, 2023

🎉 This PR is included in version 1.61.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants