S
Stormy Beetle
With growing automation and increasing use of Harness, teams' list of pipelines continue to grow. While one can name pipelines with a standardized syntax to sort them appropriately, the list becomes unmanageable.
This feature request is to add nested folder structures to clean up the view and organize pipelines by service and purpose. An example:
Pipelines
├── Database
│ ├── MongoDB
│ │ ├── Provisioning
│ │ │ ├── Create
│ │ │ ├── Delete
│ │ │ └── Modify
│ │ └── Users
│ │ ├── Create
│ │ ├── Delete
│ │ └── Password_Update
│ └── MySQL
│ ├── Provisioning
│ │ ├── Create
│ │ ├── Modify
│ │ └── delete
│ └── Users
│ ├── Create
│ ├── Delete
│ └── Update_Password
└── Kafka
├── Provisioning
│ ├── Create
│ ├── Delete
│ └── Modify
├── Topics
│ ├── Create
│ └── Delete
└── Users
├── Change_Password
├── Create
└── Delete
Created by Gino Orvieto
·