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

Use EOS As Hard Limit for Being Valid #390

Open
jdrew82 opened this issue Dec 2, 2024 · 0 comments
Open

Use EOS As Hard Limit for Being Valid #390

jdrew82 opened this issue Dec 2, 2024 · 0 comments

Comments

@jdrew82
Copy link
Contributor

jdrew82 commented Dec 2, 2024

Environment

  • Nautobot version: 2.3.12
  • nautobot-device-lifecycle-mgmt version: 2.2.0

Proposed Functionality

As the Software object has End of Software Support as a field we should enable the ability to use this date as a hard limit on Software being valid. My thinking is that you'd simply look at that field on the Software object during the validation Job and if the current date is past the EOS date then the Software is invalid, even if the Valid Until on ValidatedSoftware is in the future or undefined.

Use Case

For some enterprises the policy is that any End of Support software is considered non-compliant and should not be in use on Devices.

@jdrew82 jdrew82 changed the title Use EOSAs Hard Limit for Being Valid Use EOS As Hard Limit for Being Valid Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant