alis product¶
Manage products: view one, create or request one, rename its label, and manage who has access.
Synopsis¶
alis product new <org>.<product> [flags]
alis product rename [<org>.<product>] --display-name <name> [flags]
alis product request <org>[.<product>] [flags]
alis product share [<org>.<product>] [flags]
alis product view [<org>.<product>] [flags]
Aliases: product, products.
Description¶
A product lives in a build environment, has a two-letter id, and holds services and deployment environments. Inside a product directory the reference may be omitted.
Subcommands¶
alis product new¶
Create a new product in a build environment you administer. The product is provisioned with a single development deployment environment (a long-running operation: its cloud project, repositories and the deployment environment) and you become a product admin. Streams progress until done. Not a build environment administrator? Use alis product request.
| Flag | Type | Default | Meaning |
|---|---|---|---|
--async |
bool | false | Start provisioning and print the operation without waiting. |
--display-name <name> |
string | the capitalised id | Human-readable product name. |
--poll-interval <duration> |
duration | 5s |
How often to poll the provisioning operation. |
--timeout <duration> |
duration | 0 |
Give up waiting after this duration (the operation keeps running). |
alis product rename¶
Rename the customer-facing display label of a product. The stable id, repositories and cloud resources do not change, and no Terraform deploy is triggered.
| Flag | Type | Default | Meaning |
|---|---|---|---|
--display-name <name> |
string | New customer-facing product name (required). | |
--yes |
bool | false | Skip the approval prompt (same as --approve). |
alis product request¶
Ask a build environment's administrators for a new product. Opens a request conversation the admins approve or decline; approval provisions the product with a development deployment environment and makes you its admin. The product id is optional (two lowercase letters); the admins can choose one. An open request for the same product is returned instead of duplicating it.
| Flag | Type | Default | Meaning |
|---|---|---|---|
--display-name <name> |
string | Human-readable product name (required). | |
--reason <text> |
string | Why the product is needed. |
alis product share¶
Show who has access to a product and with which role, or grant, change and remove a person's access. With no flags, print the current access. Only administrators can change access; administrators and builders can see it. Access propagates to cloud and git permissions in the background.
| Flag | Type | Default | Meaning |
|---|---|---|---|
--email <addr> |
string | The person's email address. | |
--invite <given-name> |
string | Invite the person as a new builder first, using this given name. | |
--remove |
bool | false | Remove the person's access instead of granting a role. |
--role <role> |
string | builder |
Role to grant: admin or builder. |
--yes |
bool | false | Skip the approval prompt (same as --approve). |
alis product view¶
Show a product with its services and deployment environments.
No flags beyond the global flags.
Examples¶
alis product view acme.shop --json
alis product new acme.sh --display-name "Shop" --json
alis product request acme --display-name "Shop" --reason "New storefront" --json
alis product rename acme.sh --display-name "Storefront" --json
alis product share acme.sh --email ana@example.com --role admin --json
alis product share acme.sh --json
Errors¶
not_organisation_admin on new names the fallback: alis product request.