Use the Secrets Gradle plugin to store and access project secrets

[ryan-conway]

Issue

Original Thread

Secret management is a valid concern for all projects, with Google recommending to not check in any API keys to version control.
We can use the Secrets Gradle plugin to store and access these keys, and also make use of build-variant specific properties so we can keep the specific keys for staging or release separately.

Solution

• Integrate the Secrets Gradle plugin to template-xml and template-compose
• Update sample folders to reflect template changes

Who Benefits?

Developers

What's Next?

• Create issue to integrate Secrets Gradle plugin
• Create issue to update sample folders

[toby-thanathip]

Voted, let's add it. ✅

However, which key will we use for showcasing our sample projects? As of now, we currently don't have any API keys 💭

[toby-thanathip]

However, which key will we use for showcasing our sample projects? As of now, we currently don't have any API keys 💭

This RFC will be influenced by #434 💡

[luongvo]

Voted 👍

[chornerman]

Voted 🚀

[manh-t]

Voted 👍