Skip to content

feat: ldx-sync provides product enablement and severity filter as booleans [IDE-1816]#1179

Open
andrewrobinsonhodges-snyk wants to merge 8 commits intorefactor/IDE-1786_folder-config-refactoringfrom
feat/IDE-1816_split-products-and-filters
Open

feat: ldx-sync provides product enablement and severity filter as booleans [IDE-1816]#1179
andrewrobinsonhodges-snyk wants to merge 8 commits intorefactor/IDE-1786_folder-config-refactoringfrom
feat/IDE-1816_split-products-and-filters

Conversation

@andrewrobinsonhodges-snyk
Copy link
Copy Markdown
Contributor

Description

Provide description of this PR and changes, if linked Jira ticket doesn't cover it in full.

Checklist

  • Tests added and all succeed
  • Regenerated mocks, etc. (make generate)
  • Linted (make lint-fix)
  • README.md updated, if user-facing
  • License file updated, if new 3rd-party dependency is introduced

@snyk-pr-review-bot

This comment has been minimized.

@snyk-io
Copy link
Copy Markdown

snyk-io bot commented Mar 16, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

SettingScanAutomatic: "scan_automatic",
SettingScanNetNew: "scan_net_new",
SettingIssueViewOpenIssues: "issue_view_open_issues",
SettingIssueViewIgnoredIssues: "issue_view_ignored_issues",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Why is this not done in a map like the severity filters below?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need a map actually and not check for the prop names directly ?

The AnnotationRemoteKey annotations in register_configurations.go used
incorrect keys that didn't match the actual LDX-Sync API field names.
This caused the GAF ConfigResolver to fail mapping remote config keys.

Changes:
- severities -> removed (severities now handled via severityAPIKeys)
- cwe -> cwe_ids
- cve -> cve_ids
- rule -> rule_ids
- automatic -> scan_automatic
- net_new -> scan_net_new
- open_issues -> issue_view_open_issues
- ignored_issues -> issue_view_ignored_issues
- Added AnnotationRemoteKey for product settings (product_code_enabled, etc.)
@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants