Is this related to a problem? Please describe.
The nvcf-cli function invoke command derives the normal invocation host by prefixing the selected function ID. Vanity Gateway mappings instead require an exact configured host and an arbitrary mapped path. Users and BDD tests must currently bypass the CLI and invoke Vanity Gateway with curl, including separate API-key handling.
Describe the solution you would like
Add first-class Vanity Gateway invocation support to nvcf-cli. The command should:
- preserve an exact Vanity Gateway host instead of prefixing the function ID
- accept the configured mapped request path
- reuse the saved function API key and existing secret-safe authentication handling
- preserve current standard HTTP, LLM, and gRPC invocation behavior
- include CLI tests and user documentation
When this is available, the Vanity Gateway smoke coverage in #1363 should use the CLI and remove its direct curl helper.
Describe alternatives you have considered
Continue invoking the local Envoy listener with curl. This proves the gateway works, but duplicates CLI authentication and request construction in the BDD harness.
Additional context
Related to #1361 and #1363.
By submitting this issue, you agree to follow our code of conduct and contributing guidelines.
Is this related to a problem? Please describe.
The nvcf-cli function invoke command derives the normal invocation host by prefixing the selected function ID. Vanity Gateway mappings instead require an exact configured host and an arbitrary mapped path. Users and BDD tests must currently bypass the CLI and invoke Vanity Gateway with curl, including separate API-key handling.
Describe the solution you would like
Add first-class Vanity Gateway invocation support to nvcf-cli. The command should:
When this is available, the Vanity Gateway smoke coverage in #1363 should use the CLI and remove its direct curl helper.
Describe alternatives you have considered
Continue invoking the local Envoy listener with curl. This proves the gateway works, but duplicates CLI authentication and request construction in the BDD harness.
Additional context
Related to #1361 and #1363.
By submitting this issue, you agree to follow our code of conduct and contributing guidelines.