Add support for custom ONTAP API port configuration #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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: