Stage configuration variable not available via lazily loaded lambda

[patrickbussmann]

Steps to reproduce

config/deploy.rb

set :deploy_to, ->{ "/var/www/vhosts/#{fetch(:application)}" }

config/deploy/production.rb

set :application, "example.org"

Expected behavior

Command cap production deploy -p --dry-run prints.

------- Printing current config variables -------
:deploy_to => "/var/www/vhosts/example.org"
:application => "example.org"

Actual behavior

Command cap production deploy -p --dry-run prints.

------- Printing current config variables -------
:deploy_to => "/var/www/vhosts/"
:application => "example.org"

System configuration

https://gist.github.com/patrickbussmann/d81bb558cdf4d55c24a5a3eb596b5b18

Additional information

I read the documentation here. https://capistranorb.com/documentation/faq/how-can-i-access-stage-configuration-variables/
And it says The deploy.rb configuration is executed first and then the stage file(s) from config/deploy/*.rb are executed next.
But for this I'm using this lambda lazily loaded thing.

So I think I made it right but the system understands it wrong.

[leehambley]

Thanks for the report @patrickbussmann - fo be clear could you provide the config/deploy.rb and config/deploy/production.rb here? Please only redact passwords and IPs, includes/requires may be relevant for diagnosing the issue.