Skip to content

Conversation

@ksingh-scogo
Copy link

Add optional port parameter to ONTAP connection setup, allowing users to specify custom API ports. Port defaults to 443 if not specified, maintaining full backward compatibility.

Changes:

  • Add port parameter support to _instantiate_connection()
  • Update CLI config creation to prompt for port (optional, defaults to 443)
  • Update documentation with port configuration examples and notes

The port can be specified during config creation via interactive prompt or manually added to config.json as "port": <port_number>. This is particularly useful for environments where the ONTAP API is exposed on non-standard ports (e.g., port 8001 for MCP server usage).

Use Cases

This change is particularly useful for:

  • MCP server deployments where ONTAP API is exposed on custom ports (e.g., 8001)
  • Development/testing environments with non-standard port configurations
  • Network configurations requiring custom port mappings

Add optional port parameter to ONTAP connection setup, allowing users
to specify custom API ports. Port defaults to 443 if not specified,
maintaining full backward compatibility.

Changes:
- Add port parameter support to _instantiate_connection()
- Update CLI config creation to prompt for port (optional, defaults to 443)
- Update documentation with port configuration examples and notes

The port can be specified during config creation via interactive prompt
or manually added to config.json as "port": <port_number>. This is
particularly useful for environments where the ONTAP API is exposed
on non-standard ports (e.g., port 8001 for MCP server usage).
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