Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 2.23 KB

README.md

File metadata and controls

42 lines (32 loc) · 2.23 KB

Resourceexplorer2

Parity grade: B · SDK aws-sdk-go-v2/service/resourceexplorer2@v1.33.4 · last audited 2026-10-18 (e1a1dfbea)

Coverage

Metric Value
PARITY entries audited 27 (27 ok)
Feature families 5 (5 ok)
Known gaps 13
Structural gaps (can't be emulated) 1
Deferred items 0
Resource leaks clean

Known gaps

  • GetServiceIndex: not implemented; service-linked indexes are created by AWS services and no emulator path creates one
  • GetServiceView: not implemented; same reason as GetServiceIndex
  • ListServiceIndexes: not implemented; same reason as GetServiceIndex
  • ListServiceViews: not implemented; same reason as GetServiceIndex
  • ListStreamingAccessForServices: not implemented; no service streaming access is ever granted
  • ListSupportedResourceTypes: 46 curated types, not the full AWS catalog
  • Search: keywords match as case-insensitive substrings over the ARN and tag text, not as AWS tokens; the application filter is unsupported and an unknown filter is treated as a keyword
  • Search: only services wired into the tagging aggregation (and the five EC2 kinds) are indexed; other emulated services are invisible
  • GetManagedView: the two managed views (SSM, Resilience Hub) are emulator-defined; real names, ARNs and policies are unverified
  • ListIndexesForMembers: no organization membership or delegated-administrator check
  • CreateView: organization and OU scopes are accepted without validating them against Organizations
  • ConflictException: several conflict and validation cases (view without an index, aggregator rules, duplicate type update) use codes chosen from documented behaviour, not from SDK evidence
  • MaxResults: the 1-100 (views 1-20) ranges are not in the SDK and are unverified

Structural gaps

These do not block an A grade — no implementation could produce real data here because the underlying data source cannot exist in an emulator.

  • Indexing is instantaneous and always complete: there is no crawler, so LastReportedAt is the query time and replication lag between Regions cannot occur.

More