[Enhancement] Add Default Environment variables to buildtools.json #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds the ability to add non-sensitive default values to the buildtools.json that are used by the Secrets class generator and the template manifest task. This allows both generically default variables and build configuration based variables.
The defaults can now be added in the buildtools.json as follows:
Given this sample I might tokenize the package name in the AndroidManifest or the CFBundleIdentifier in the Info.plist, this would then allow me to automatically set the name to
com.avantipoint.awesomeappdev
while debugging the app, andcom.avantipoint.awesomeapp
on all other builds. As a result I can easily ensure that I can deploy side by side instances of the app.Issues