Refactor (non-breaking change which improves the structure or operation of the implementation)
Breaking change (fix or feature that would cause existing functionality to change)
Description
Moves all mobileapp configuration from settings over to solution configuration
Adds support for controlling the filenames of file based settings. This allows for users to identify a specific version of a certificate or profile that is in use
Adds support for defining a badge that is added to app icons
Motivation and Context
The primary motivation for this move is to make the complex configuration options required to publish mobile apps documented, type checked and validated via the engine before they are passed to downstream processes. This makes it easier to discover the available options and to support the migration from bash run tasks to our runbook tasks in the future.
How Has This Been Tested?
Tested locally
Related Changes
Prerequisite PRs:
None
Dependent PRs:
None
Consumer Actions:
Current settings will need to be mapped to the new configuration settings this can either be through qualification of the values on the solution file or the use of dynamic values to resolve the existing settings in place.
File based settings ( certificates, json keys etc, will still need to be stored as settings)
Intent of Change
Description
Motivation and Context
The primary motivation for this move is to make the complex configuration options required to publish mobile apps documented, type checked and validated via the engine before they are passed to downstream processes. This makes it easier to discover the available options and to support the migration from bash run tasks to our runbook tasks in the future.
How Has This Been Tested?
Tested locally
Related Changes
Prerequisite PRs:
Dependent PRs:
Consumer Actions: