epam / epam/cloud-pipeline

Retention period for the FS mounts

Open
#690 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

goal/dorado :sparkles: kind/enhancement state/draft sys/core sys/gui
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

Background
Retention periods are already in place for the Object Storages.
A similar feature should be implemented for the File Storages.

Approach
While the FS mount is being created/edited, users shall have the ability to set a data retention period. After that period expiration date, there are two possible ways:

  1. data will be removed
  2. data will be transferred to the "archive" Object Storage

That should look similar to STS/LTS durations settings for Object Storages.

  • if STS and LTS durations for the FS mount aren't specified - the data shall be stored as previously
  • if STS duration for the FS mount is specified - the data shall be stored in the File Storage during that period, after its expiration:
    • if LTS duration isn't specified - the data shall be removed
    • if LTS duration is specified - the data shall be transferred and stored in the "archive" Object Storage. After the LTS duration expiration, the data shall be removed
  • LTS duration for the FS mount couldn't be specified without STS duration
  • LTS duration for the FS mount couldn't be less than STS duration

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing Object Storage STS/LTS duration settings, then trace the File Storage mount creation and edit flows. Done means FS mounts support the specified STS and optional LTS behavior, including validation that LTS requires STS and is not shorter, with removal or archive transfer after expiration.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.