https://cloudposse.com logo
Join Slack
Powered by
Checking to see if this behavior change in `v1.210...
# atmos
d
Checking to see if this behavior change in 
v1.210.0
was intentional. I'm guessing its not? 
hooks.store-output.name
evaluates to 
staging
but since now we don't process yaml functions when hydrating and running hooks, it evaluates to 
!template staging
, raising 
**Error:** store "!template staging" not found in configuration
Copy code
hooks:
    store-outputs:
      # Determine where we store outputs based on the project_id
      name: !template "{{ index .settings.context.project_to_store .settings.context.project_id }}"
It seems like I don't necessarily have to use 
!template
in this case
cc @Igor Rodionov
a
this looks like a regression
d
maybe a regression but definitely a deliberate change
a
if 
{{ index .settings.context.project_to_store .settings.context.project_id }}
returns a string, you probably don't need 
!template
, please test it
d
yeah i removed 
!template
to unblock our deploys
Copy code
atmos describe stacks -s sentencing --process-functions=false | \
yq '.["staging"].components.terraform["component"].hooks.store-outputs.name'
reproduces and returns 
staging
👍 1
a
can you please open an issue on GH?
i
@Dan Hansen could you downgrade to 1.209.0 before I will fix that ?
d
I think this just broke again in v1.220.0 the opposite way
Copy code
**Error:** store "{{ index .settings.context.project_to_store .settings.context.project_id }}" not found in configuration
filed here https://github.com/cloudposse/atmos/issues/2538
Open in Slack
PreviousNext
Powered by