epam / epam/cloud-pipeline

[NGS Portal] Pipeline results in storage rules

Open
#3,906 0 comments 0 reactions 0 assignees View on GitHub
goal/portal 🔬 kind/enhancement
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

### Background

Currently, there is an ability to create storage rules for a pipeline.
These rules are being used to upload data to the output data storage once pipeline is finished. It helps to store only specific data user needs.
We shall expand that functionality to output specific results of NGS pipelines. Such outputs then can be viewed via Reports section (#3902).

### Approach

We shall add new columns to the table of pipeline's storage rules:
- **Name** - rule name. _String_, can be empty
- **Pipeline Result** - option that enables the output of NGS pipeline results. _Boolean_, shall be shown as checkbox

Approximate view of the updated form shall be:
![Image](https://github.com/user-attachments/assets/93bffa89-bee6-4b4d-95ba-6606333085b0)

During a new rule creation, user shall be able:
- to specify a name for a rule
- to set the option that enables the output of NGS pipeline results

![Image](https://github.com/user-attachments/assets/063325e6-4930-4e47-9d90-fa0216ac9175)

Form behavior shall be the following:
- _Name_ field content is optional (by default), user shall have the ability to leave it empty
- if _Pipeline results_ option is ticked:
- _Name_ field becomes mandatory and can't be left empty
- _Move to STS_ checkbox shall be ticked and disabled automatically
![Image](https://github.com/user-attachments/assets/d2051f49-0e66-4b47-b28c-4a9b2f9bf802)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by locating the pipeline storage-rules form and the code that creates and persists storage rules, then trace how pipeline outputs reach the Reports section described in #3902. Done means rules support an optional Name and Pipeline Result checkbox, with the stated validation and automatic Move to STS behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.