Files
Add files to Containers.
Refer to the files feature for configuration details.
The examples show these variations to provide file content:
score.yaml
: Base approach supplying the file contents as a multiline string. This approach creates the same file content across all environments.score-shared-values.yaml
: (Recommended) Supplying the file contents via a Shared Value via theenvironment
resource which is available as part of the Score specification . Since Shared Values may optionally be overridden on an Environment level, this approach lets you inject environment-specific configuration managed through the Platform Orchestrator.score-local-file-source.yaml
: Supplying the file contents via a file available locally which is read at Score deployment time, i.e. when executinghumctl score deploy
.
appsettings.json
(
view on GitHub
)
:
{
"key1": "value1",
"key2": "value2",
"key3": "value3"
}
score-local-file-source.yaml
(
view on GitHub
)
:
apiVersion: score.dev/v1b1
metadata:
name: my-workload
containers:
demo:
image: registry/my-image:1.0.0
files:
- target: /app/default.config
mode: "0644"
# The source references a locally available file
# It is read by the humctl CLI when running "humctl score deploy"
source: "./appsettings.json"
score-shared-values.yaml
(
view on GitHub
)
:
apiVersion: score.dev/v1b1
metadata:
name: my-workload
containers:
demo:
image: registry/my-image:1.0.0
files:
- target: /app/default.config
mode: "0644"
# The content references the Shared Value APP_SETTINGS, available through the "env" resource declared below
content: "${resources.env.APP_SETTINGS}"
resources:
env:
# The type "environment" is available per the Score specification
type: environment
score.yaml
(
view on GitHub
)
:
apiVersion: score.dev/v1b1
metadata:
name: my-workload
containers:
demo:
image: registry/my-image:1.0.0
files:
- target: /app/default.config
mode: "0644"
content: |
[config]
key=value