You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a new option to the new PUT /api/v1/config API endpoint which will enforce that the new expiration policy changes are not only saved in the settings but that new metadata versions are generated using the expiration policy changes.
This could be especially useful if an organization has initially set a long expiration date for a role, but for whatever reason they want to shorten it.
Then, instead of waiting long for the roles to expire the organization will be able to enforce the new expiration rules directly.
We need discussion what should be the default.
Important: First implement #399 and then reuse the code from it for this option.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What is the task about?
Add a new option to the new
PUT /api/v1/config
API endpoint which will enforce that the new expiration policy changes are not only saved in the settings but that new metadata versions are generated using the expiration policy changes.This could be especially useful if an organization has initially set a long expiration date for a role, but for whatever reason they want to shorten it.
Then, instead of waiting long for the roles to expire the organization will be able to enforce the new expiration rules directly.
We need discussion what should be the default.
Important: First implement #399 and then reuse the code from it for this option.
Code of Conduct
The text was updated successfully, but these errors were encountered: