AppSetting replacement doesn't work for variable named 'Environment'

Legacy Uncategorised
#1

Hi,

We have a customer that created an AppSetting named ‘Environment’ that they want to replace with the environment name. We noticed upon deployment that despite there being a variable named ‘Environment’ in the deployment log, the setting isn’t getting replaced. Is ‘Environment’ a reserved setting name that can’t be used?

-Dan

#2

Hi Dan,

Thanks for reaching out. The word “Environment” should be available for this. Could you send us the deployment Raw log with the debugging variables enabled so we can check what is happening with that variable at deployment time?

Thanks!

Dalmiro

#3

Hi,

Attached is the deployment log, let me know if you have any questions.

-Dan

ServerTasks-319.log.txt (48 KB)

#4

Hi Dan,

It looks like you have a typo on the variable name

  • [EnVRIonment] = ‘QA’

Try to correct it and then create a new release.

Thanks!

Dalmiro

#5

Hi Dalmiro,

OK I feel dumb now :slight_smile: Thanks for the help!

-Dan

#6

Happens to the best of us! Glad I could help :slight_smile:

#8