UI: complete Discovery network object and relationship surface#208
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #207.
This completes the Discovery Merged Network UI surface for the recently added network APIs, excluding screenshot capture. Operators can now inspect managed network objects, inspect and resolve explicit relationships, choose request-scoped schema policy, use relink-specific conflict actions, navigate from conflict details back to affected merged rows, and filter relationship/object context without dropping to raw API calls.
What Changed
account_level,region_level,global, andmanual.schema_policythrough hierarchy, flat, and conflict network queries.resolvedrelationship state vocabulary.POST /api/v1/network/relationships/resolveendpoint so IDs containing path separators are supported.alternate_exact_poolUX to use relink-oriented wording and displayprevious_pool_id, targetpool_id, discovered resource ID, and relationship count.missing_parentconflicts and display returned network object details.pool_idandsource_discovered_idfilters across memory, SQLite, and PostgreSQL stores.0.17.2changelog entry.Tests
npm run test -- DiscoveryNetworkRelationshipTable DiscoveryNetworkConflictList useNetworknpm run buildenv XDG_CACHE_HOME=/tmp/nix-cache nix develop -c go test ./internal/apiok cloudpam/internal/api.Notes
go test ./internal/apiwas not available in this shell becausegois not on PATH, so the backend API slice was run through the repo Nix dev shell.web/dist/index.htmlwas updated by the UI build. The hashed assets underweb/dist/assets/are generated but not tracked by Git in this repo.Remaining Follow-Up