tree eba32a1f41ab56718c0ec31977615ea1d6426376
parent 726d20a68ff73e5a75fc772eddfb1a3fb5b32872
author Tianjie Xu <xunchang@google.com> 1589147295 +0000
committer Tianjie Xu <xunchang@google.com> 1590617642 +0000

Reland "Calculate the runtime fingerprint prefixes from build prop"

This reverts commit b21e48b499850bfb5ac9e6e155ed96e8e724c5c0.

In practice, some partners use the 'import' statement to override
the device fingerprint at runtime. The runtime fingerprint will
later add to the metadata of OTA package, so that the OTA server
can deliver the package to corresponding devices correctly.

This CL supports parsing a subset of import statement that the init
process recognizes. And we loose the restriction based on how the
dynamic fingerprint is used in practice. Right now, we only searches
for the override of brand, name and device. And the placeholder
format should be ${placeholder}, with its value supplied by the
script caller.

As part of the implementation, we generate all the possible
combinations of the input boot variables. And recalculate the
fingerprint for each of the combination. Though we load the
build.prop multiple times, the logic is easier to follow. Also,
it's more convenient to enhance the logic if we only want to
allow some of the boot variables combination later.

Bug: 152167826
Change-Id: I4a9fa35c7ac037ff1cf4f9a4bdff602beac3894b
Merged-In: I4a9fa35c7ac037ff1cf4f9a4bdff602beac3894b
Test: unittests pass