Skip to content

Simplify defaultConnection fetch and backward-compat env vars #1626

@kmcginnes

Description

@kmcginnes

Parent PRD

What to build

Update fetchDefaultConnection to use ${apiBase}defaultConnection as the single fetch URL, removing the SageMaker fallback URL guessing. Update the DefaultConnectionData schema to accept both old field names (GRAPH_EXP_PUBLIC_OR_PROXY_ENDPOINT, GRAPH_EXP_USING_PROXY_SERVER) and the canonical GRAPH_EXP_CONNECTION_URL. Update mapToConnection to handle both formats. Update process-environment.sh to support old Docker env var names (PUBLIC_OR_PROXY_ENDPOINT, USING_PROXY_SERVER) with deprecation warnings, mapping them to the new canonical names.

Type: HITL — requires review before completion.

Acceptance criteria

  • fetchDefaultConnection fetches from ${apiBase}defaultConnection only (no SageMaker fallback)
  • DefaultConnectionData schema accepts old field names alongside new ones
  • mapToConnection produces correct ConnectionConfig from both old and new defaultConnection.json formats
  • process-environment.sh maps old env var names to new canonical names
  • process-environment.sh logs deprecation warnings when old env var names are used
  • GRAPH_EXP_CONNECTION_URL is the canonical field name for the database URL
  • Tests verify schema parsing for both old and new field names
  • Tests verify mapToConnection output for both formats

Blocked by

User stories addressed

  • User story 3
  • User story 4
  • User story 5

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions