You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 313bfcb
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/v3/source/includes/concepts/_lifecycles.md.erb
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Name | Type | Description
41
41
**type** | _string_ | `buildpack`
42
42
**data.buildpacks** | _list of strings_ | A list of the names of buildpacks, URLs from which they may be downloaded, or `null` to auto-detect a suitable buildpack during staging
43
43
**data.stack** | _string_ | The root filesystem to use with the buildpack, for example `cflinuxfs4`. <br/>When the `diego_custom_stacks` feature flag is enabled, this can also be a container image URI with the `docker://` scheme. A custom stack requires custom buildpacks or admin buildpacks that are not associated with a stack. Its image layers count toward the app instance's disk quota.
44
-
**data.credentials** | _object_ | Credentials used to download custom buildpacks from private Git repositories or to pull custom stacks from private registries, keyed by host. Each entry contains a username/password pair. If any buildpack URL embeds credentials, **data.credentials** must be empty; provide credentials in one place only.
44
+
**data.credentials** | _object_ | Credentials used to download custom buildpacks from private Git repositories or to pull custom stacks from private registries, keyed by host. Each entry contains a username/password pair. If any buildpack URL embeds credentials, **data.credentials** must be empty; provide credentials in one place only.<br/>For private custom stacks, configure credentials on the app lifecycle for running instances and tasks.
45
45
46
46
During staging with a custom stack, Cloud Foundry uses the final repository component of the image URI, excluding its tag or digest, as `CF_STACK`. For example, `docker://registry.example.com/team/cflinuxfs4:1.268.0` sets `CF_STACK` to `cflinuxfs4`. The custom stack and buildpack must be compatible.
47
47
@@ -86,7 +86,7 @@ Name | Type | Description
86
86
---- | ---- | -----------
87
87
**type** | _string_ | `cnb`
88
88
**data.buildpacks** | _list of strings_ | A list of URLs with either `docker://` or `http(s)://` scheme, pointing to the Cloud Native Buildpack OCI image. <br/>When the scheme is `http(s)://`, an OCI tarball is expected to be present at the specified location.
89
-
**data.credentials** | _object_ | Credentials used to download the configured buildpacks or to pull custom stacks, keyed by registry host. Each entry contains a username/password pair or a token. Custom stack credentials must be a username/password pair. CNB buildpack URLs must not embed credentials; use **data.credentials** instead.
89
+
**data.credentials** | _object_ | Credentials used to download the configured buildpacks or to pull custom stacks, keyed by registry host. Each entry contains a username/password pair or a token. Custom stack credentials must be a username/password pair. CNB buildpack URLs must not embed credentials; use **data.credentials** instead.<br/>For private custom stacks, configure credentials on the app lifecycle for running instances and tasks.
90
90
**data.stack** | _string_ | The root filesystem to use with the buildpack, for example `cflinuxfs4`. <br/>When the `diego_custom_stacks` feature flag is enabled, this can also be a container image URI with the `docker://` scheme. A custom stack requires custom buildpacks or admin buildpacks that are not associated with a stack. Its image layers count toward the app instance's disk quota.
91
91
92
92
During staging with a custom stack, Cloud Foundry uses the final repository component of the image URI, excluding its tag or digest, as `CNB_STACK_ID`. For example, `docker://registry.example.com/team/cflinuxfs4:1.268.0` sets `CNB_STACK_ID` to `cflinuxfs4`. The custom stack and buildpack must be compatible.
Copy file name to clipboardExpand all lines: docs/v3/source/includes/resources/builds/_create.md.erb
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Name | Type | Description
40
40
41
41
Name | Type | Description | Default
42
42
---- | ---- | ----------- | -------
43
-
**lifecycle** | [_lifecycle object_](#the-lifecycle-object) | Lifecycle information for a build | lifecycle on the app
43
+
**lifecycle** | [_lifecycle object_](#the-lifecycle-object) | Lifecycle information for a build. <br/>Credentials supplied here apply only to staging and do not update the app's stored credentials. | lifecycle on the app
44
44
**staging_memory_in_mb** | _integer_ | Memory in MB allocated for staging of the build
45
45
**staging_disk_in_mb** | _integer_ | Disk space in MB allocated for staging of the build
46
46
**staging_log_rate_limit_bytes_per_second** | _integer_ | Log rate limit in bytes per second allocated for staging of the build
0 commit comments