Expand my Community achievements bar.

SOLVED

Dispatcher core:warn Config variable ${VAR_NAME} is not defined

Avatar

Community Advisor

Hello,

 

I am trying to ProxyPass to external server in vhost file and used environment variable (defined in Cloud Manager) to replace in vhost file as external system host domain. When I am checking Cloud Manager pipeline build logs, I can see this warning in logs

Config variable ${VAR_NAME} is not defined

 

But deployment went fine. Is it normal warning or could be a potential issue?

 

cc: @Tanika02

arunpatidar

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Found something https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-... 

 

Dispatcher

Only regular environment variables can be used with the dispatcher. Secrets cannot be used.

However environment variables cannot be used in IfDefine directives.

TIP

You should validate your use of environment variables with the dispatcher locally before deploying.

 

 



Arun Patidar

View solution in original post

8 Replies

Avatar

Community Advisor

Please check this you might have this variable in dispatcher files.



Arun Patidar

Avatar

Community Advisor

Yes @arunpatidar I used this variable in vhost file and It's defined in Cloud Manager environment variables.

Avatar

Community Advisor

Then you need to use this variable in vhost file as 

  • ${env.VARIABLE_NAME}


Arun Patidar

Avatar

Community Advisor

I tried using this Arun, but warning persist in build logs.

Config variable ${env.VAR_NAME} is not defined

 

 

Avatar

Correct answer by
Community Advisor

Found something https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-... 

 

Dispatcher

Only regular environment variables can be used with the dispatcher. Secrets cannot be used.

However environment variables cannot be used in IfDefine directives.

TIP

You should validate your use of environment variables with the dispatcher locally before deploying.

 

 



Arun Patidar

Avatar

Level 1

Was this actually ever resolved for you?  What was the solution.  The accepted answer doesn't seem to answer the question