harness - The Modern Software Delivery Platform®
Create
Log in
Home
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
Continuous Delivery & GitOps
Continuous Integration
Cloud Cost Management
Feature Flags
Service Reliability Management
Security Testing Orchestration
Chaos Engineering
Software Engineering Insights
General Platform Requests
Internal Developer Portal
Code Repository
IACM
Continuous Error Tracking
Drone 2.x
Open Source
SSCA
Database DevOps
FME
Application and API Posture
Application and API Security
Application and API Protection
Traceable Platform
Uncategorized
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 (1,593)
Continuous Integration (342)
Cloud Cost Management (197)
Feature Flags (89)
Service Reliability Management (9)
Security Testing Orchestration (86)
Chaos Engineering (36)
Software Engineering Insights (98)
General Platform Requests (401)
Internal Developer Portal (84)
Code Repository (36)
IACM (28)
Continuous Error Tracking (12)
Drone 2.x (13)
Open Source (31)
SSCA (7)
Database DevOps (11)
FME (0)
Application and API Posture (0)
Application and API Security (0)
Application and API Protection (0)
Traceable Platform (0)
Trigger multiple pipelines with a single webhook
We'd like the ability to trigger multiple pipelines with a single webhook event. In our case, we have multiple input sets for each service deployment we want to do. When a webhook is sent to Harness, we want Harness to trigger 1 pipeline per input set. We also don't want to configure multiple triggers for this since it will add redundancy and make debugging triggers difficult.
0
1
Enable Bulk Reconciliation of templates
Hi, We are seeing that whenever we made change to harness org level templates, we have to ask consumers to reconcile it manually for every single pipeline, please enable bulk-reconciliation-of-templates: https://developer.harness.io/docs/platform/templates/reconcile-pipeline-templates/#bulk-reconciliation-of-templates Thanks, Sohel
0
1
Infrastrucutre defination not available in compiled yaml using filtered list
When we use filter lists of environment or infrastructure while running the pipeline, the infrastructure defination is not present in the compiled yaml, due to this it is hard to implement OPA policy on it. Please add infrastructure definations as well in compliled yaml incase of filtered list.
0
1
HTTP Matching for Canary Traffic Routing
We'd like to request HTTP matching for Canary Traffic Routing configuration. Currently, Harness only supports routes but we would like Harness to support URI matching as well. For example, http: - match: - uri: prefix: /api/v1/
0
1
Support unique directory structure for SOPS decryption files
Due to the CD Pipeline failing due to a SOPs decryption issue, the only way to achieve the runtime decryption of secrets.yaml in the current design is to include the SOPs-related file as part of the chart itself. This will ensure it's downloaded with the manifest file and available in its dedicated folder, preventing conflicts with other executions. Customer repositories maintain override secrets.yaml files outside the charts directory. There's no option today to download the override files into a uniquely identifiable folder. This request is to download override files such as secrets.yaml into a unique isolated directory. This feature request is important for enabling the customer team to begin using Harness pipelines in production and to validate the workflow thoroughly in lower environments ahead of the production rollout.
0
1
ANSI color codes in GitOps logs
We'd like for the GitOps pod logs to support ANSI color codes
0
1
Container run steps should allow leaving shell and command blank to to use the image's entrypoint
For container Run step, use the image entrypoint defined in the dockerfile instead of requiring shell and command fields. This works only for background step at the moment. It would be useful for Run steps as well. The use case is to run some tests where the image is already set up to run them. It should be blocking (not background) since it is for running smoke tests.
1
1
Remove older cache from harness pipeline
Hi, As we are moving from bitbucket pipeline to harness, in bitbucket we have an option to remove the older cache from the pipeline. In Harness pipeline also we want to remove older cache. We have enabled our cache intelligence in harness pipeline build stage. Now we want to remove older cache from harness pipeline. Please guide us on this
0
1
Remove older cache from harness pipeline
In Harness pipeline we want to remove older cache. We have enabled our cache intelligence in harness pipeline build stage. Now we want to remove older cache while the pipeline deployments. In Bitbucket when we are deploying, they give one option to remove the older cache from bitbucket pipeline. We want to do the same in harness pipeline.
0
1
Harness support for Web Logic Deployment
We are planning to create a deployment solution for Web Logic and wanted to check what offerings Harness provide for the same. Please let me know when I can schedule a call with you.
0
1
Load More
→
Powered by Canny