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

Should updated_at for service instances be updated when the last operation changes? #4087

Open
johha opened this issue Nov 13, 2024 · 1 comment

Comments

@johha
Copy link
Contributor

johha commented Nov 13, 2024

Example service instance:

{
  "guid": "3a2f5713-c979-45cc-9524-f513f9ad1238",
  "created_at": "2024-10-17T15:57:46Z",
  "updated_at": "2024-10-17T15:57:46Z",
  "name": "my-service-instance",
  "tags": [],
  "last_operation": {
    "type": "update",
    "state": "succeeded",
    "description": "",
    "updated_at": "2024-10-28T08:39:15Z",
    "created_at": "2024-10-28T08:39:15Z"
}

Should the updated_at field of the service instance be updated when the last_operation changes?

@Samze
Copy link
Contributor

Samze commented Nov 13, 2024

Given the operation is acting on the service and this structure is really more a reflection of how we represent the data internally (two separate tables). I would vote to have the updated_at field update when last_operation changes.

Also note that this is probably also the case for async service bindings.

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

No branches or pull requests

2 participants