# AWS Lambda deployment provider: equals sign in environment\_variables value
**URL:** https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247
**Category:** Deployment
**Created:** [July 17, 2019, 3:12pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247 "2019-07-17T15:12:40Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 17, 2019, 3:12pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/1 "2019-07-17T15:12:40Z")
Hi!
Is it possible to escape equals sign (=) somehow in environment\_variables value.
Example: DB\_URL=123=456
environment\_variables:
- “DB\_URL=123=456”
Ends up as DB\_URL=123 in AWS Lambda Console. Expected DB\_URL variable with value 123=456.
In practice this is a real issue for example with URLs with query parameters
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 4:34pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/2 "2019-07-17T16:34:54Z")
Quoting should work. `DB_URL="123=456"`
---
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 17, 2019, 4:52pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/3 "2019-07-17T16:52:42Z")
environment\_variables:
- DB\_URL=“123=456”
Results in value: "123
The same result with:
environment\_variables:
- ‘DB\_URL=“123=456”’
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 6:33pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/4 "2019-07-17T18:33:46Z")
Sorry, but something else is modifying the env var.
[https://travis-ci.org/BanzaiMan/travis\_production\_test/builds/560118792#L187-L188](https://travis-ci.org/BanzaiMan/travis_production_test/builds/560118792#L187-L188)
---
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 17, 2019, 6:54pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/5 "2019-07-17T18:54:15Z")
I was talking about Lambda deployment provider. For example:
```
deploy:
- provider: lambda
access_key_id: ${AWS_ACCESS_KEY_ID}
secret_access_key:
secure: ${AWS_SECRET_ACCESS_KEY}
function_name: "Function-Name"
handler_name: "handler"
region: "eu-west-1"
runtime: "nodejs8.10"
role: "arn:aws:iam::12345678:role/LambdaRole"
zip: "lambda.zip"
environment_variables:
- 'DB_URL="123=456"'
```
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 6:56pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/6 "2019-07-17T18:56:17Z")
My apologies. The code is here.
>
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 7:00pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/7 "2019-07-17T19:00:08Z")
You can test the fix by:
```auto
deploy:
- provider: lambda
edge:
branch: lambda-equal
⋮ # rest
```
---
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 17, 2019, 7:40pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/8 "2019-07-17T19:40:29Z")
Fix is working as expected! Well done, thank you!
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 8:01pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/9 "2019-07-17T20:01:24Z")
It’ll be fixed in the next release (most likely 1.10.13).
---
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 17, 2019, 8:09pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/10 "2019-07-17T20:09:37Z")
> [@BanzaiMan](#):
>
> most likely 1.10.13
Will the lambda-equal branch be open until the release?
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 17, 2019, 9:00pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/11 "2019-07-17T21:00:27Z")
Yes.
---
### Author:  [@teemuniiranen](https://travis-ci.community/u/teemuniiranen)
#### Post date: [July 18, 2019, 6:12am UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/12 "2019-07-18T06:12:42Z")
Seems like the branch has been removed when merged to master branch of the [https://github.com/travis-ci/dpl](https://github.com/travis-ci/dpl)?
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [July 18, 2019, 10:52pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/13 "2019-07-18T22:52:49Z")
Oops. You’re right. I’ve restored the branch.
You may also use:
```auto
deploy:
edge: true
```
instead as well.
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [September 27, 2019, 8:22pm UTC](https://travis-ci.community/t/aws-lambda-deployment-provider-equals-sign-in-environment-variables-value/4247/14 "2019-09-27T20:22:51Z")
Release 1.10.13 includes this, and I’ve deleted the branch.