-
Notifications
You must be signed in to change notification settings - Fork 43
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 / updated into API for sorting / auditing #59
Comments
for faas-netes: a creation timestamp is available in the Deployment spec, but a modification date is not. Unless we drill down in the status part of the Deployment spec. |
Related: kubernetes/kubernetes#12430 For the time being, As a side-note, it looks like containerd does have an updated at
@jsiebens to prevent duplicated work, are you taking this? |
Enables contributors to proceed with changes for #59 in the various back-ends Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
To unblock folks so they can start with faasd and faas-netes, and because nobody has volunteered to take the schema change yet, I've gone ahead and added a field for CreatedAt and cut a release. https://github.com/openfaas/faas-provider/releases/tag/v0.17.2 Please feel free to populate in faasd + faas-netes in separate PRs. |
Populates the CreatedAt value from the container's info field. Ref: openfaas/faas-provider#59 Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
Populates the CreatedAt value from the container's info field. Ref: openfaas/faas-provider#59 Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
@alexellis I think this is done and released in our supported providers. |
Schema change
Add created / updated into API for sorting / auditing
I had a use-case where I wanted to sort the functions by time created, and I couldn't find a way to do that with the function spec. This could also be useful for auditing purposes.
faas-netes
This is available in the Deployment spec already
faasd
The container creation date is probably available, but there isn't a way to update a container without re-creating it, so the created and modified dates would be the same.
The text was updated successfully, but these errors were encountered: