update the created_at field when updating resource #629
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: bin <bin.pan@daocloud.io>
|
Hi @flpanbin, DetailsInstructions for interacting with me using comments are available here. |
Iceber
approved these changes
Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
When
clustersynchro-managerupdating resource, the created_at field would not be updated, which may lead to the created_at of the resource inconsistent with the creationTimestamp of the object.Which issue(s) this PR fixes:
Fixes #626
Special notes for your reviewer:
test results:
the created_at for
elastic-operator-0andamamba-argocd-application-controller-0has been updated:Does this PR introduce a user-facing change?: