File Transform task for json file it puts the result in the temp folder and not the artifacts
See original GitHub issueHi,
I’m trying to use the “File Transfrom” (Preview mode) to do variable substitution in json file but checking the logs it shows that it is substituting in the temp folder and never copy back to artifact folder.
This is from logs:
Applying JSON variable substitution for D:\Build Agents\vsts-01_work_temp\temp_web_pac...
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Bug in File Transform task for json file as it put the result in the ...
Hi,. I'm trying to use the below task to do variable substitution in json file but checking the logs it shows that it...
Read more >FileTransform@2 - File transform v2 task - Microsoft Learn
For zipped folders, the contents are extracted to the TEMP location, transformations executed, and the results zipped in original artifact ...
Read more >azure devops - FileTransform Task in release pipeline doesn't ...
The steps you use File Transform task should be correct. The value of appsettings.Development.json can be updated successfully.
Read more >JSON formatting with jq and CI/CD linting automation | GitLab
Also make sure you are using the right extension for JSON files. When using a compressed JSON file, it must end with “json”...
Read more >Model Catalog — ADS 1.0.0 documentation
No matter which approach you choose, the end result is a model artifact that ... the temporary directory used for the model artifacts,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue is fixed and the fix is available in all the accounts. Please feel free to reopen the issue if it still exists.
As work around now I ran some copy tasks on the temp folder to bring the files with replaced tokens back to artifact dir. Thanks guys