Aaron Knauf
12/28/2022, 3:52 PMcontainers:
my-app:
variables:
VAR1: ${resources.env.VAR1}
VAR2: ${resources.env.VAR2}
VAR3: ${etc.}
etc.
resources:
env:
Thomas Harris
12/29/2022, 12:24 PMenv
is a special resource type
for circumstances where a variable cannot/should not be resolved by the platform.
The env resource type allows you to declare properties of the variable. For example, the variable may be marked sensitive=true
, declare which type of input: type=string
, type=map
etc and set default values. Without being able to declare these properties then variables become very limited (do we just assume every variable is a string? every variable is sensitive?)
i would argue the variable is not being defined twice, rather defined and referencedAaron Knauf
12/29/2022, 12:56 PMAaron Knauf
12/29/2022, 2:22 PMSusanne Tünker
01/05/2023, 1:55 PM.env
file contents are now being sorted (based on Issue #8).
Check the release log for a detailed update and follow the installation guide to download the latest version of score-compose.
score-helm 0.2.0:
• Added substitutions support for metadata properties as described here.
Check the release log for a detailed update and follow the installation guide to download the latest version of score-helm.Patrick Rachford
01/12/2023, 4:58 PMbrew install score-spec/tap/score-compose
brew install score-spec/tap/score-helm
brew install score-spec/tap/score-humanitec
Taras Mankovski
01/22/2023, 4:50 PMTaras Mankovski
02/10/2023, 3:19 AMTaras Mankovski
02/10/2023, 4:02 AMDavid Jarosch
02/15/2023, 4:01 PMDavid Jarosch
02/15/2023, 4:03 PMGiulia Guizzardi
04/20/2023, 11:30 AMMartin Iluminatti
04/27/2023, 8:30 PMscore.yaml
file?Timothy Fong
05/03/2023, 5:34 PMTimothy Fong
05/03/2023, 5:35 PMTimothy Fong
05/03/2023, 5:35 PMTimothy Fong
05/03/2023, 5:35 PMMichael Weinberg
05/31/2023, 12:22 AMscore-foo run
commands generating config files, rather than actually performing a deploy. I would expect that to actually execute the workload, and for a config rendering command to be something like generate
Susanne Tünker
07/25/2023, 9:04 AM-skip-validation
flag to the command.
• Removed resource properties from Score spec (Issue #61): Resource properties were added to the Score spec as an option for users to implement validation. Since they aren't utilised by any of the current reference implementations and have caused confusion with users did we decide to deprecate them.
• Overrides via command line parameters (Issue #60): Allows users to override individual properties via command line arguments via the --p
flag as described in our documentation. For example: score-compose run -f score.yaml --property containers.my-service.image=python3
overrides the default image name to python3
.
Please let us know if you have any questions 🙂Susanne Tünker
08/08/2023, 11:17 AMMarkus Stahl
08/22/2023, 6:49 AMMarcus Queiroz
09/20/2023, 7:20 PMTravis Edgar
10/02/2023, 2:54 PMTravis Edgar
10/02/2023, 2:54 PMDavid Young
10/13/2023, 7:20 PMMarkus Stahl
10/27/2023, 8:07 AMscore-humanitec
. The tutorial and examples in the doc deal with 1 workload per application. At the moment i do:
> score-humanitec delta -f workload1.yaml --deploy
> score-humanitec delta -f workload2.yaml --deploy
which results in 2 deployments where there should only be one (i think).
How can you do it differently? can I add 2 workloads in the score.yaml? Or would I have to use the humanitec API? I also tried to provide several yaml files with -f workload1.yaml -f workload2.yaml
, but then only the last score spec is being pulled.Alejandro Michell
12/04/2023, 11:57 PMBen Meier
12/08/2023, 10:03 AMcontainers.*.variables
and containers.*.files.*.content
?
Any other opinions?Sam Connolly
12/08/2023, 11:52 AMMathieu Benoit
12/19/2023, 8:14 PM