strato
strato copied to clipboard
Multicloud Lifecycle config expiration minimum and schedule
Issue/Feature Description: Multicloud Lifecycle config expiration minimum is 1 Day. And actual deletion will be 0:00 every day. Therefore, if endusers set "1day", actual deletion will be over 24 hours (next day's 0:00) For example, if they set it at 3pm, the deletion will be after 33 hours.
Practically, endusers need to configure hours and actual deletion should be same as the configure that they select.
Why this issue to fixed / feature is needed(give scenarios or use cases): Considering the usecase such as daily development, endusers want hours config at least.
How to reproduce, in case of a bug: This is a feature request.
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)