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

Add created_at metadata to saved objects #9376

Closed
cjcenizal opened this issue Dec 5, 2016 · 4 comments · Fixed by #143507
Closed

Add created_at metadata to saved objects #9376

cjcenizal opened this issue Dec 5, 2016 · 4 comments · Fixed by #143507
Labels
enhancement New value added to drive a business result Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@cjcenizal
Copy link
Contributor

cjcenizal commented Dec 5, 2016

See #9202

Add a created_at root level field to all SOs, similar to updated_at

We can surface this metadata in the UI to differentiate between objects with the same name.

@epixa epixa added Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed :Management release_note:enhancement labels Oct 16, 2018
@joshdover joshdover added the stale Used to mark issues that were closed for being stale label Jan 14, 2021
@pgayvallet pgayvallet removed the stale Used to mark issues that were closed for being stale label Oct 14, 2022
@pgayvallet pgayvallet changed the title Add date created metadata to saved objects Add created_at metadata to saved objects Oct 14, 2022
@pgayvallet
Copy link
Contributor

Reopening as this wasn't completed and discussions around this came back recently

@pgayvallet pgayvallet reopened this Oct 14, 2022
@pgayvallet
Copy link
Contributor

From our slack discussion:

  • Add a new root-level created_at field to the SavedObject type
  • Field will be automatically populated by the system when an object is created
    • similar to what is done for updated_at
  • Field will have to be optional (same as updated_at) because we can't properly populate it for existing objects
  • Main concern is regarding what we do with this value for import and copy to space operations
    • for now, we should just preserve the value
    • later on, we can eventually add options to the impacted APIs / UIs to have the user choose the behavior
      • e.g choose between keeping the import file's creation dates or repopulate it for all imported objects during an import

@pgayvallet
Copy link
Contributor

cc @elastic/kibana-core given I'm not sure the team is subscribed to the issue given its age.

@afharo
Copy link
Member

afharo commented Oct 14, 2022

Main concern is regarding what we do with this value for import and copy to space operations

++ I'd even say: it may be different when overwriting vs. importing/copying to space.

But I like the plan to just preserve the value for now 😇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants