search

solarhess / rules_build_secrets

Bazel build rules to make it easier to incorporate secrets into your build process.
MIT License
17 stars 6 forks source link

Android resource file output #1

Open ellenhp opened 5 years ago

ellenhp commented 5 years ago

Hope it's ok that I'm creating an issue, it doesn't specifically say how to provide feedback. I'm considering using a rule like this to manage secrets in a multi-project monorepo that's starting to outgrow gradle.

My project is open source so I need to figure out how to manage the API keys in a reasonable way. I don't want to use .gitignore because it's probably the riskiest way to do things, so I'm interested in using this rule. I was wondering if it's possible to extend the rule to output a file that I could include as an input to the android_binary rule as a resource file.

android_binary(
    name = "mediarecorder",
    manifest = "AndroidManifest.xml",
    resource_files = glob(["res/**"]), # I'd like the output of the secrets rule to make its way here.
    deps = [":main"],
)

It's been a while since I've done anything interesting with a BUILD file so hopefully this is possible and I'm not just embarrassing myself.

I don't mind doing the work and sending you a PR if you're willing to review it, but I could use a few pointers to docs because it's been a while since I've never had to deal with a .bzl file. Again, I'm not sure if you're actively maintaining this but I just wanted to let you know what my use case is since you ask for feedback in the README. Thanks!

ellenhp commented 5 years ago

Looking at the example, it might be possible to do this with an echo in the same way? I'll investigate.