# Maximum length of application environmental variables

**URL:** <https://forums.balena.io/t/maximum-length-of-application-environmental-variables/243168>\
**Category:** Product support\
**Created:** [January 26, 2021, 11:36pm UTC](https://forums.balena.io/t/maximum-length-of-application-environmental-variables/243168 "2021-01-26T23:36:17Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![barryjump](https://avatars.discourse-cdn.com/v4/letter/b/bc8723/32.png) [@barryjump](https://forums.balena.io/u/barryjump)\
**Post date:** [March 31, 2021, 8:18am UTC](https://forums.balena.io/t/maximum-length-of-application-environmental-variables/243168/36 "2021-03-31T08:18:52Z")

</div>

Hi @vipulgupta2048 thank you for updating the docs on env variables.

I posted this elswhere ([Openbalena CLI optimization - #11 by barryjump](https://forums.balena.io/t/openbalena-cli-optimization/268322/11)) but I noticed openbalena in particular does not permit creating envs with this kind of format while Balena Cloud does:

`DD_TAGS: name:joe env:test another:true`

My use case is for Datadog which expects their tagging mechanism to be set with multiple tags defined in a single value field of the DD\_TAGS separated by a space.

Any thoughts on if that could be fixed or at least documented as invalid for the time being?

---

_[View the full topic](https://forums.balena.io/t/maximum-length-of-application-environmental-variables/243168)._