harness - The Modern Software Delivery Platform®
Create
Log in
Feedback
Feature Requests
Log in to your harness - The Modern Software Delivery Platform® account to give feedback
Log In
Boards
Feature Requests
Powered by Canny
Feature Requests
Anonymous
Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
This Fiscal Quarter
Next Fiscal Quarter
Long-term
Pending Feedback
Complete
posts in
All Categories
All Categories
Continuous Delivery & GitOps (2,129)
Continuous Integration (491)
Feature Mgmt & Experimentation (355)
Cloud Cost Management (256)
Feature Flags (123)
Service Reliability Management (10)
Security Testing Orchestration (135)
Chaos Engineering (42)
Software Engineering Insights (148)
General Platform Requests (569)
Internal Developer Portal (178)
Code Repository (63)
IACM (65)
Continuous Error Tracking (17)
Drone 2.x (14)
Open Source (32)
Supply Chain Security (27)
Database DevOps (21)
API Discovery (2)
API Testing (5)
API Protection (2)
Traceable Platform (1)
Artifact Registry (16)
AI SRE (6)
SAST (0)
AI Discovery (2)
AI Testing (1)
AI Protection (0)
Workspace should show drift history/timeline
Currently we only get notification that workspace is drifted, but it would help us to know more details like its in drifted state from last 1 week/1 month/ 1year. Add-on details like what exact drift will be even useful.
3
·
IACM
·
pending feedback
1
Support for Slack webhook/notification as workspace setting
Currently notifications setting are pipeline level, in cases where multiple workspaces share a common pipeline, need to send notifications to workspace specific settings. So notifications settings should be supported on workspace level, which should override pipeline level settings
2
·
IACM
·
pending feedback
1
Module download stats not present in Harness IaCM Module registry
Module download stats not present in Harness IaCM Module registry
2
·
IACM
·
pending feedback
4
Allow overriding IACM stage configurations
We utilize a very specific git branching strategy within our application development and engineering org that allows development engineers to code to the equivalent of a 'develop' branch to validate "pre-Pull Request" changes to IaC. We need to contain the risk of drift in that related iacm workspace over time by including the 'dev' workspace content be still deployed using 'main' in the standard SDLC. Since the IACM stage itself has the branch configuration, we want to be able to temporarily override that value in the occasion that we need to utilize the 'develop' branch. This is not a long-lived branch but rather a "sandbox" rendering of the IaC codebase, similar to AWS's trunk-based guidelines: https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-a-trunk-branching-strategy-for-multi-account-devops-environments.html
2
·
IACM
·
pending feedback
1
Powered by Canny