stado credentials signing-profile ensure
Invocation
stado credentials signing-profile ensure [OPTIONS] --provider <PROVIDER> --host <HOST> --profile <PROFILES> --credentials <CREDENTIALS> <ITEM>Purpose
Make or find a product's code-signing provisioning profiles through the provider's API and store them, base64, as fields of one owner-vault item
Required inputs and options
| Input or option | Contract |
|---|---|
<ITEM> | Item the profiles are stored in (for example tama-desktop-signing) |
--provider <PROVIDER> | Provider the profiles are made through. No provider is assumed Possible values: - apple: Apple: provisioning profiles through the App Store Connect API |
--host <HOST> | Host whose owner vault receives the item |
--profile <PROFILES> | FIELD=BUNDLE_ID: store the profile for BUNDLE_ID as FIELD. Repeat for each bundle the product signs |
--credentials <CREDENTIALS> | Item holding the team API key (fields key_id, issuer_id, private_key_p8_base64). No item is built in |
--type <PROFILE_TYPE> | Profile type; MAC_APP_DIRECT is a Developer ID profile [default: MAC_APP_DIRECT] |
--certificate-type <CERTIFICATE_TYPE> | Certificate type the profile names; DEVELOPER_ID_APPLICATION for Developer ID [default: DEVELOPER_ID_APPLICATION] |
--json | Command option; required or optional as shown in the invocation. |
Output and state effect
It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.
Refusals
- Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.