Skip to content

docs(locations): cloud resource drift matching and the endpoint migration boundary - #16032

Open
svader0 wants to merge 2 commits into
DefectDojo:devfrom
svader0:sc-14534-cloud-resource-docs
Open

svader0 wants to merge 2 commits into
DefectDojo:devfrom
svader0:sc-14534-cloud-resource-docs

Conversation

@svader0

@svader0 svader0 commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Description

Docs only. Two pages get a short addition about cloud resource Locations (a DefectDojo Pro location type):

  • docs/content/asset_modelling/locations/PRO__migrating_from_endpoints.md: a new bullet under "What the Migration Does Not Do". Endpoints that hold cloud resource identifiers (ARNs and similar) migrate as URL Locations. They are not converted into Cloud Resource Locations. A cloud connector import is the way to model them.
  • docs/content/triage_findings/finding_deduplication/PRO__location_drift_matching.md: a new "Cloud resource findings" section. Cloud resources match on their provider identifier only. Region, service, tags and display name do not take part in the match.

Companion to a DefectDojo Pro change on the same release line (dev).

Test results

No code changed. I checked the Markdown renders and the headings sit under the existing sections.

Documentation

This PR is the documentation.

…tion boundary

Add two decisions to the OSS docs for the CloudResource location work.

The endpoint migration guide now says the migration does not convert
cloud resources held in Endpoint rows. Those rows keep migrating as
URL Locations. A cloud connector re-import is the way to get a real
Cloud Resource Location.

The location drift matching guide now documents cloud resource
matching. A cloud resource matches on its provider-assigned
identifier alone, with no fuzzy matching.
Say what a user sees after the Pro change. Two findings on two different cloud
resources are never duplicates. An earlier merge does not survive the next
import.
@svader0 svader0 added this to the 3.4.0 milestone Sep 21, 2026
@github-actions github-actions Bot added the docs label Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant