Skip to content

Inconsistent naming between CLI flags and environment variables for HTTP configuration #184

@MacondoExpress

Description

@MacondoExpress

Description:

There are naming inconsistencies between CLI flags and their corresponding environment variables for HTTP-related configuration options in args.go.

Current Behavior:

CLI Flag Environment Variable
--neo4j-http-port NEO4J_MCP_HTTP_PORT
--neo4j-http-host NEO4J_MCP_HTTP_HOST
--neo4j-http-allowed-origins NEO4J_MCP_HTTP_ALLOWED_ORIGINS
--neo4j-http-tls-enabled NEO4J_MCP_HTTP_TLS_ENABLED
--neo4j-http-tls-cert-file NEO4J_MCP_HTTP_TLS_CERT_FILE
--neo4j-http-tls-key-file NEO4J_MCP_HTTP_TLS_KEY_FILE

Expected behavior:

CLI Flag Environment Variable
--neo4j-http-port NEO4J_HTTP_PORT
--neo4j-http-host NEO4J_HTTP_HOST
--neo4j-http-allowed-origins NEO4J_HTTP_ALLOWED_ORIGINS
--neo4j-http-tls-enabled NEO4J_HTTP_TLS_ENABLED
--neo4j-http-tls-cert-file NEO4J_HTTP_TLS_CERT_FILE
--neo4j-http-tls-key-file NEO4J_HTTP_TLS_KEY_FILE

Metadata

Metadata

Assignees

No one assigned

    Labels

    breakingThis will be a breaking change.bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions