feat: add connector mode resolution helpers for gateway (draft)#6
feat: add connector mode resolution helpers for gateway (draft)#6
Conversation
EF-0001 follow-up:
|
|
@copilot fix failed checks and conflicts |
Agent-Logs-Url: https://github.com/SocioProphet/cloudshell-fog/sessions/eed87b7d-6788-448b-b498-262010f4feac Co-authored-by: mdheller <21163552+mdheller@users.noreply.github.com>
Agent-Logs-Url: https://github.com/SocioProphet/cloudshell-fog/sessions/eed87b7d-6788-448b-b498-262010f4feac Co-authored-by: mdheller <21163552+mdheller@users.noreply.github.com>
…nore Agent-Logs-Url: https://github.com/SocioProphet/cloudshell-fog/sessions/eed87b7d-6788-448b-b498-262010f4feac Co-authored-by: mdheller <21163552+mdheller@users.noreply.github.com>
Done.
Fixed. Ran |
Summary
This draft PR starts EF-0001 from the engineering fix backlog: make runtime connector mode selection explicit and fail-fast.
What is included now:
cmd/gateway/connector_mode.goCONNECTOR_MODEstubandk8sKUBECONFIG, if setcmd/gateway/connector_mode_test.gostubWhy this PR exists
The reviewed gateway entrypoint still wires the stub connector unconditionally, even though the repository already contains a real Kubernetes connector backend. This PR captures the first implementation slice needed to close that gap.
Still TODO before merge
cmd/gateway/main.goto callbuildConnector(logger)instead of unconditionally instantiating the stub connectormain.gois updatedRelated repository-native planning artifacts
docs/meta/engineering-fix-backlog-v0.mddocs/meta/spec-code-conformance-v1.mddocs/spec/state-machine-v0.mddocs/spec/openapi/control-api.v1.yamlNotes
This PR is intentionally draft because the gateway entrypoint is not yet hooked up to the new helper.