Skip to content

Tracking last patch date #3037

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.

Sign up for GitHub

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

Jump to bottom
Open
Ansible-man opened this issue Sep 26, 2024 · 1 comment · May be fixed by #3579
Open

Tracking last patch date #3037

Ansible-man opened this issue Sep 26, 2024 · 1 comment · May be fixed by #3579
Labels
enhancement ✨ New feature or request

Comments

@Ansible-man
Copy link
Contributor

Is your feature request related to a problem? Please describe.

An option to track the last time a zarf package was updated. We are forced to comply with strict policies around patching and its always a pain to prove the last patch date to show we are in compliance. If zarf provided an additional column to zarf package list that shows its initial deployment date and last updated date then life would be made easy for those who work in the environments Zarf is targeting.

Describe the solution you'd like

  • Given a state - A zarf package is deployed/updated
  • When an action is taken - zarf package list is executed maybe with a flag or an info subcommand
  • Then something happens - Zarf shows all the packages deployed to the cluster along with their last patch date

Describe alternatives you've considered

There are other ways to do this for sure but having the information built into zarf natively would be amazing

Additional context

Add any other context or screenshots about the feature request here.
@Ansible-man Ansible-man added the enhancement ✨ New feature or request label Sep 26, 2024
@github-project-automation github-project-automation bot moved this to Triage in Zarf Sep 26, 2024
@AustinAbro321
Copy link
Contributor

Since moving to v0.42.2 we now have time stamps on the package secrets created for each package deploy. The Zarf secret for each package now creates a managedFields key for each of the package secrets. These managedFields show include the timestamp of when the package was created. See the timestamp with k get secrets -n zarf zarf-package-example --show-managed-fields -o yaml. There is also a .creationTimestamp field under .metadata. This at least makes it possible to get the data.

Example:

  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        f:data: {}
      f:metadata:
        f:labels:
          f:app.kubernetes.io/managed-by: {}
          f:package-deploy-info: {}
      f:type: {}
    manager: zarf
    operation: Apply
    time: "2024-11-08T19:51:04Z"

LMK if you'd still like to see this information in zarf package list

@jbrewer3 jbrewer3 linked a pull request Mar 17, 2025 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement ✨ New feature or request
Projects
Zarf
Status: Triage
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

3037 last patch date jbrewer3/zarf
2 participants
@AustinAbro321 @Ansible-man