Skip to content

feat: onboard the crossconnectsv2 API - #66

Draft
displague wants to merge 1 commit into
chore/shared-onboarding-scaffoldfrom
feat/onboard-crossconnectsv2
Draft

displague wants to merge 1 commit into
chore/shared-onboarding-scaffoldfrom
feat/onboard-crossconnectsv2

Conversation

@displague

Copy link
Copy Markdown
Member

Stacked on #60; retarget to main once that merges.

Why

Brings the Cross Connects v2 service into the SDK, generated from its published OpenAPI document, so it has a maintained client alongside the other services. The generated client follows the specification and is not expected to match older standalone samples one-for-one.

What

  • Makefile.crossconnectsv2, spec-sync workflow, fetched/patched spec, generated client in services/crossconnectsv2, registered in the root and aggregate poms (via script/onboard_service.sh)
  • examples/crossconnectsv2:
    • OrderCrossConnect: orders a standard fiber cross connect; covers the earlier standard, intracustomer, extended and fiber order samples
    • RequestDeinstall: orders removal of a cross connect by asset ID; covers the earlier deinstall sample
    • UpdateOrderContacts: adds a notification contact to an existing order
    • HandleCrossConnectErrors: ApiException status/headers/body and the ErrorDetails model, with a non-JSON fallback; uses an invalid token so nothing is created
  • The three order examples create or modify orders, so they only send their request when EQUINIX_EXAMPLE_ALLOW_WRITES=true
  • No order retrieval or pagination examples: the service only has operations that create or modify orders, and no read or list operations

Testing

  • generated with the pinned generator version; mvn compile of the service and its examples
  • examples not run against a live endpoint

🤖 Generated with Claude Code

- Makefile.crossconnectsv2, spec-sync workflow, fetched spec, generated client in services/crossconnectsv2, pom registrations
- examples/crossconnectsv2: OrderCrossConnect, RequestDeinstall, UpdateOrderContacts (all guarded by EQUINIX_EXAMPLE_ALLOW_WRITES) and HandleCrossConnectErrors
- no retrieval or pagination examples: the service has no read or list operations

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@displague

Copy link
Copy Markdown
Member Author

@srushti-patl Is this PR of interest? (I'm not sure where this stands with respect to the CrossConnect changes introduced in #79 )

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant