Skip to content

Write local.properties from repo vars and secrets - #3

Merged
mountEvarus merged 1 commit into
mainfrom
mountEvarus/local-properties
Aug 22, 2026
Merged

Write local.properties from repo vars and secrets#3
mountEvarus merged 1 commit into
mainfrom
mountEvarus/local-properties

Conversation

@mountEvarus

Copy link
Copy Markdown
Owner

Prerequisite for migrating finance.

The three API-backed apps inject their base URL two different ways:

variable mechanism
health, footprint API_BASE_URL written into local.properties
finance FINANCE_API_BASE_URL passed as a Gradle property

Same value, two names, two mechanisms. The shared workflow now owns it: it writes local.properties from vars.API_BASE_URL, secrets.DEVICE_API_KEY and secrets.GOOGLE_MAPS_API_KEY.

Only keys that are set get written, so film-roll (which uses none of them) is unaffected and keeps its build defaults. Runs in both verify and release so the two jobs compile identical buildConfigFields. The step logs which keys it wrote, never the values.

The apps inject their API base URL two different ways: health and footprint write
local.properties from an API_BASE_URL variable, finance passes a FINANCE_API_BASE_URL
Gradle property. Same value, two mechanisms and two variable names.

The workflow now writes local.properties from API_BASE_URL, DEVICE_API_KEY and
GOOGLE_MAPS_API_KEY, in both the verify and release jobs so they compile the same
buildConfigFields. Keys absent from the repo are not written, so an app that does not use
one keeps its build default.
@mountEvarus
mountEvarus merged commit 153d6a0 into main Aug 22, 2026
1 check passed
@mountEvarus
mountEvarus deleted the mountEvarus/local-properties branch August 22, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant