Skip to content

fix remoteObj revision field #232

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

Merged
merged 2 commits into from
Jan 27, 2025
Merged

fix remoteObj revision field #232

merged 2 commits into from
Jan 27, 2025

Conversation

kobzonega
Copy link
Contributor

@kobzonega kobzonega commented Jul 4, 2024

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

field resourceVersion inside .status.remoteResources.conditions does not explain actual information

Issue Number: N/A

What is the new behavior?

  • fix field resourceVersion inside .status.remoteResources.conditions

Other information

@kobzonega kobzonega force-pushed the fix-remoteObjRV-log branch 4 times, most recently from 40bf88f to 3a584fe Compare July 17, 2024 16:29
@kobzonega kobzonega changed the title Fix remote obj rv log ObservedGeneration in conditions Jul 18, 2024
@kobzonega kobzonega changed the title ObservedGeneration in conditions fix remoteObj revision field Dec 4, 2024
@kobzonega kobzonega force-pushed the fix-remoteObjRV-log branch from 4c59ff7 to 0c49f2f Compare December 4, 2024 05:48
@kobzonega kobzonega merged commit 06b6f63 into master Jan 27, 2025
3 checks passed
@kobzonega kobzonega deleted the fix-remoteObjRV-log branch January 27, 2025 17:10
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.

2 participants