cluster ticket
[Preview]
ockam cluster ticket [OPTIONS]
Options
-
--zone-name [ZONE_NAME](optional)
The name of the Zone -
--zone-config [ZONE_CONFIG](optional)
The path to the Zone configuration file, in yaml or json format. If not set, the./ockam.yamlfile from the current directory will be used -
--use-http-api(optional)
Force the command to use the HTTP API. By default, the command will use the Orchestrator API -
--api-endpoint [API_ENDPOINT](optional)
The API endpoint of the Ockam AI Platform. Can be set using theAI_API_BASE_URLenvironment variable. Defaults tohttp://localhost:30080 -
-a,--attribute [ATTRIBUTE](optional)
Attributes inkey=valueformat to be attached to the member. You can specify this option multiple times for multiple attributes -
--relay [ENROLLEE_ALLOWED_RELAY_NAME](optional)
Name of the relay that the identity using the ticket will be allowed to create. This name is transformed into attributes to prevent collisions when creating relay names. For example:--relay foois shorthand for--attribute ockam-relay=foo
Learn More:
Use ockam <SUBCOMMAND> --help for more information about a subcommand (e.g., 'cluster' or 'zone').
Learn more about Command: https://docs.ockam.ai/command/ Learn more about Ockam: https://docs.ockam.ai/
Feedback:
If you have questions, as you explore, join us on the Discord channel https://discord.ockam.io