Skip to content

Remove legacy HTTP path from symphony-api.go - #862

Open
lirenjie95 wants to merge 3 commits into
eclipse-symphony:mainfrom
lirenjie95:chore/retire-symphony-api-legacy-path
Open

Remove legacy HTTP path from symphony-api.go#862
lirenjie95 wants to merge 3 commits into
eclipse-symphony:mainfrom
lirenjie95:chore/retire-symphony-api-legacy-path

Conversation

@lirenjie95

Copy link
Copy Markdown
Contributor

Fixes #857

Follow-up to #466 item 2 and #859. With CallRemoteProcessor migrated to the API client, the legacy HTTP free functions in symphony-api.go now have zero callers and can be retired.

Changes:

  • Moved pure helper functions (MatchTargets, CreateSymphonyDeployment, CreateSymphonyDeploymentFromTarget, AssignComponentsToTargets, GetTargetRuntimeKey, ConstructSummaryId) to the new file deployment_helpers.go in the same package, so no callers need to change.
  • Removed all legacy HTTP free functions with baseUrl/user/password signatures from symphony-api.go, along with the auth and callRestAPI helpers. All corresponding functionality is now provided by ApiClient methods.
  • Cleaned up tests: removed the three legacy HTTP integration tests from symphony-api_test.go, and moved the remaining helper tests to deployment_helpers_test.go.

Verified no remaining references to the removed functions with grep.

@lirenjie95
lirenjie95 requested a review from Haishi2016 as a code owner August 21, 2026 13:05
…t.go

The package-level test constants user/password were removed along with
symphony-api_test.go, but TestGetInstancesWithEmptyNamespaceDefaultsToDefault
still referenced them, causing undefined symbol compile errors in CI.
Use empty string literals instead, consistent with other tests in the file.
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.

Retire the legacy HTTP path in symphony-api.go

1 participant