Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

Option to use parameters file as well as variables #113

Closed
jonmartin136 opened this issue Aug 14, 2019 · 2 comments
Closed

Option to use parameters file as well as variables #113

jonmartin136 opened this issue Aug 14, 2019 · 2 comments

Comments

@jonmartin136
Copy link

Hi

I know something similar has been rasied previoulsy but the scenario here is slightly different. I'm already dynamically creating a VSTS variable that is then used by the Replace Tokens task but it has now reached the upper size limits for variables:

##[warning]Environment variable 'XXXX' exceeds the maximum supported length. Environment variable length: 41681 , Maximum supported length: 32766

If the task supported reading a parameters (token/value pairing) file as well as using the environment variables then instead of dynamically creating a variable I'd generate the parameters file.

The file format could be a simple text TOKEN = VALUE per line or more complex as JSON or XML format.

Thanks,

@qetza
Copy link
Owner

qetza commented Aug 16, 2019

Hi @jonmartin136,

This is a good feedback, i'll add it to the backlog. Just need to defined what would be the user friendliest format.

@qetza
Copy link
Owner

qetza commented Mar 6, 2020

Hi @jonmartin136,
This feature is now available in version 3.4.0

@qetza qetza closed this as completed Mar 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants