deepfence / deepfence/ThreatMapper

Advanced Filters key values not sent through request from UI

Open
#519 1 comment 0 reactions 2 assignees Claimed by @saurabh2253 View on GitHub
bug for-qa needs-triage
Dominant language
TypeScript
Stars
5.3k
Forks
631
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to ThreatMapper -> Integrations -> Generate Report
2. Select Resource Type Compliance and set other filters
3. Select host in Advanced Filter
4. Download Report
5. In Request Payload the filter for host name is not applied

**Components/Services affected**

- [x] UI/Frontend
- [ ] API/Backend
- [ ] Agent
- [ ] Deployment/YAMLs
- [ ] CI/CD Integration
- [ ] Other (specify)

**Expected Behaviour**
"node_id" key to be used in resources filter

**Additional context**
Similar case for account id filters in GCP / Azure / AWS types

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.