:question: [Question]: How to debug this Stac conf.extra-directives.d error?

[tlvu]

Questions

I have another error from another staging server, updating from birdhouse-deploy 1.42.2 to 2.20.1.

Now the proxy do not even start due to the error below. I haven't seen this error in the other staging server (#623).

Both server configs are 99% similar (except hostname, password, path, ...), so this really surprise me.

$ docker logs proxy 2>&1 | tail -3
/docker-entrypoint.sh: Configuration complete; ready for start up
2025/12/19 17:25:11 [emerg] 1#1: invalid number of the map parameters in /etc/nginx/conf.extra-directives.d/stac/stac.conf:6
nginx: [emerg] invalid number of the map parameters in /etc/nginx/conf.extra-directives.d/stac/stac.conf:6

$ cat components/stac/config/proxy/conf.extra-directives.d/stac.conf
    map $http_origin $stac_origin_allowed {
        # default should not be set to the empty string because the cors.include file will interpret
        # that as "unset" and will change it to * by default. To get around this, set this to birdhouse's
        # own origin (which has the same effect as being unset since same-origin requests are already allowed). 
        default https://HOSTNAME_FQDN;
        ~.* ;
    }

[tlvu]

Oh, the other server that do not have this error, the stac.conf is slightly different !

$ cat components/stac/config/proxy/conf.extra-directives.d/stac.conf
    map $http_origin $stac_origin_allowed {
        # default should not be set to the empty string because the cors.include file will interpret
        # that as "unset" and will change it to * by default. To get around this, set this to birdhouse's
        # own origin (which has the same effect as being unset since same-origin requests are already allowed). 
        default https://HOSTNAME_FQDN;
        ~.* $http_origin;
    }

[tlvu]

I am lost, both servers have the same value for STAC_ADDITIONAL_CORS_ORIGINS.

$ ../bin/birdhouse -q -b configs -c 'echo ${STAC_ADDITIONAL_CORS_ORIGINS}'
~.* $http_origin;

Why is it different once template expanded !

[tlvu]

./pavics-compose.sh restart proxy fixes the bad template expansion ! That's really weird. Is there a race conditions bug here?

Any comments before I close this issue?

[mishaschwartz]

STAC_ADDITIONAL_CORS_ORIGINS='~.* $http_origin;' birdhouse -q -b configs -c 'echo ${STAC_ADDITIONAL_CORS_ORIGINS}'
~.* ;

Because STAC_ADDITIONAL_CORS_ORIGINS is a delayed eval variable so it interprets $http_origin as a shell variable, not a string.

This probably happens in the case where the variables are loaded into the current environment multiple times (as discussed in #605)

[tlvu]

Because STAC_ADDITIONAL_CORS_ORIGINS is a delayed eval variable so it interprets $http_origin as a shell variable, not a string.

Odd that it seems intermittent. If it's a problem, it's not consistent. I have 2 staging and 2 dev servers and this is the first time I see this happening.