| `S3_REVIEW_ENVIRONMENT_DOMAIN` | The review environment domain. | _none_ |
| `S3_REVIEW_ROOT_PATH` | S3 bucket root path (prefix) for `review` env _(only define if different from default)_ | `S3_ROOT_PATH` |
| `S3_REVIEW_PREFIX` | S3 prefix to use for `review` env _(only define if different from default)_ | `S3_PREFIX` |
Note: By default, review `environment.url` will be built as `${S3_REVIEW_ENVIRONMENT_SCHEME}://${$CI_PROJECT_NAME}-${CI_ENVIRONMENT_SLUG}.${S3_REVIEW_ENVIRONMENT_DOMAIN}`
@@ -136,7 +136,7 @@ Here are variables supported to configure the integration environment:
| :lock: `S3_INTEG_SECRET_KEY` | S3 service Secret Key for `integration` env _(only define if different from default)_ | `$S3_SECRET_KEY` |
| `S3_INTEG_BUCKET_NAME` | Bucket name for `integration` env | `${S3_BASE_BUCKET_NAME}-integration` |
| `S3_INTEG_ENVIRONMENT_URL` | The integration environment url **including scheme** (ex: `https://my-project-integration.s3-website.nonpublic.domain.com`). Do not use variable inside variable definition as it will result in a two level cascade variable and gitlab does not allow that. | _none_ |
| `S3_INTEG_ROOT_PATH` | S3 bucket root path (prefix) for `integration` env _(only define if different from default)_ | `S3_ROOT_PATH` |
| `S3_INTEG_PREFIX` | S3 prefix to use for `integration` env _(only define if different from default)_ | `S3_PREFIX` |
#### Staging environment
@@ -155,7 +155,7 @@ Here are variables supported to configure the staging environment:
| :lock: `S3_STAGING_SECRET_KEY` | S3 service Secret Key for `staging` env _(only define if different from default)_ | `$S3_SECRET_KEY` |
| `S3_STAGING_BUCKET_NAME` | Bucket name for `staging` env | `${S3_BASE_BUCKET_NAME}-staging` |
| `S3_STAGING_ENVIRONMENT_URL` | The staging environment url **including scheme** (ex: `https://my-project-staging.s3-website.nonpublic.domain`). Do not use variable inside variable definition as it will result in a two level cascade variable and gitlab does not allow that. | _none_ |
| `S3_STAGING_ROOT_PATH` | S3 bucket root path (prefix) for `staging` env _(only define if different from default)_ | `S3_ROOT_PATH` |
| `S3_STAGING_PREFIX` | S3 prefix to use for `staging` env _(only define if different from default)_ | `S3_PREFIX` |
#### Production environment
@@ -174,7 +174,7 @@ Here are variables supported to configure the production environment:
| `S3_PROD_BUCKET_NAME` | Bucket name for `production` env | `$S3_BASE_BUCKET_NAME` |
| `S3_PROD_ENVIRONMENT_URL`| The production environment url **including scheme** (ex: `https://my-project.s3-website.public.domain.com`) Do not use variable inside variable definition as it will result in a two level cascade variable and gitlab does not allow that. | _none_ |
| `AUTODEPLOY_TO_PROD` | Set this variable to auto-deploy to production. If not set deployment to production will be `manual` (default behaviour). | _none_ (disabled) |
| `S3_PROD_ROOT_PATH` | S3 bucket root path (prefix) for `production` env _(only define if different from default)_ | `S3_ROOT_PATH` |
| `S3_PROD_PREFIX` | S3 prefix to use for `production` env _(only define if different from default)_ | `S3_PREFIX` |