Erik Osterman (Cloud Posse)
03/25/2025, 9:07 PMVinny
03/25/2025, 9:32 PMErik Osterman (Cloud Posse)
03/27/2025, 11:29 AMVinny
03/27/2025, 2:31 PMVinny
03/27/2025, 7:56 PMAndriy Knysh (Cloud Posse)
03/27/2025, 8:05 PMVinny
03/27/2025, 8:06 PMAndriy Knysh (Cloud Posse)
03/27/2025, 8:14 PMAndriy Knysh (Cloud Posse)
03/28/2025, 1:22 AMatmos list values c1 --format yaml
dev:
stage: dev
test:
a: a-dev
b: b-team2
c: c-team1
d: d
prod:
stage: prod
test:
a: a-prod
b: b-prod
c: c-prod
d: d
sandbox:
stage: sandbox
test:
a: a-team2
b: b-team2
c: c-team1
d: d
staging:
stage: staging
test:
a: a-staging
b: b-team2
c: c-team1
d: dAndriy Knysh (Cloud Posse)
03/28/2025, 1:22 AMatmos list vars c1 --format yaml
dev:
value:
stage: dev
test:
a: a-dev
b: b-team2
c: c-team1
d: d
prod:
value:
stage: prod
test:
a: a-prod
b: b-prod
c: c-prod
d: d
sandbox:
value:
stage: sandbox
test:
a: a-team2
b: b-team2
c: c-team1
d: d
staging:
value:
stage: staging
test:
a: a-staging
b: b-team2
c: c-team1
d: dAndriy Knysh (Cloud Posse)
03/28/2025, 1:23 AMvalue? we don't need it?Andriy Knysh (Cloud Posse)
03/28/2025, 1:23 AMatmos list vars c1Andriy Knysh (Cloud Posse)
03/28/2025, 1:24 AMAndriy Knysh (Cloud Posse)
03/28/2025, 1:24 AMINFO before executing every command? Let's make it DEBUGAndriy Knysh (Cloud Posse)
03/28/2025, 1:25 AMatmos list settings c1 --format yaml shows some (empty) output
dev: {}
prod: {}
sandbox: {}
staging: {}
test: {}Andriy Knysh (Cloud Posse)
03/28/2025, 1:26 AMAndriy Knysh (Cloud Posse)
03/28/2025, 1:27 AMatmos list metadata c1 shows this
INFO Filtering metadata component=c1 query="" maxColumns=0 format="" stackPattern="" templates=true
No metadata found for component 'c1'Andriy Knysh (Cloud Posse)
03/28/2025, 1:27 AMAndriy Knysh (Cloud Posse)
03/28/2025, 1:34 AMatmos list values sdsddsds
INFO Filtering values component=sdsddsds componentFilter=sdsddsds query="" includeAbstract=false maxColumns=0 format="" stackPattern="" processTemplates=true processYamlFunctions=true
ERRO no values found for component 'sdsddsds'Andriy Knysh (Cloud Posse)
03/28/2025, 1:34 AMAndriy Knysh (Cloud Posse)
03/28/2025, 1:36 AMatmos list settings weweweewew
INFO Filtering settings query="" component=weweweewew maxColumns=0 format="" stackPattern="" processTemplates=true processYamlFunctions=true
ERRO failed to list settings error="error filtering and listing settings: no settings found for component 'weweweewew'"Andriy Knysh (Cloud Posse)
03/28/2025, 1:36 AMatmos list metadata weweweewew
INFO Filtering metadata component=weweweewew query="" maxColumns=0 format="" stackPattern="" templates=true
No metadata found for component 'weweweewew'Andriy Knysh (Cloud Posse)
03/28/2025, 1:39 AMERRO
• if vars, values, metadata or settings does not exist, it should be a message like
No metadata found for component 'c1'Vinny
03/28/2025, 10:21 AMVinny
03/28/2025, 10:39 AMErik Osterman (Cloud Posse)
03/28/2025, 11:23 AMErik Osterman (Cloud Posse)
03/28/2025, 11:24 AMVinny
03/28/2025, 11:26 AMErik Osterman (Cloud Posse)
03/28/2025, 11:29 AMVinny
03/28/2025, 11:32 AMVinny
03/28/2025, 11:36 AMVinny
03/28/2025, 11:37 AMVinny
03/28/2025, 11:57 AMif errors.As(err, &componentNotFoundErr) {
log.Error(componentNotFoundErr.Error())
return
}Vinny
03/28/2025, 11:58 AMVinny
03/28/2025, 11:58 AMVinny
03/28/2025, 11:58 AMErik Osterman (Cloud Posse)
03/28/2025, 1:46 PMmain(). The Go best practice is to return errors up the stack and handle exits in main, rather than calling log.Fatal or os.Exit midstream. We’re not doing this consistently today, and fixing it properly would require a larger refactor. So if you want to take the shortcut and use log.Fatal, that’s fine for now — it’s still better than silently failing. But if you’d prefer to do it the right way and return to main, that’s the preferred long-term direction.Vinny
03/28/2025, 1:48 PMVinny
03/28/2025, 1:51 PM