You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "jcesarmobile (Jira)" <ji...@apache.org> on 2020/06/24 16:15:00 UTC
[jira] [Closed] (CB-11859) Generalized solution for plugins to add
secrets to source files
[ https://issues.apache.org/jira/browse/CB-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jcesarmobile closed CB-11859.
-----------------------------
Resolution: Won't Do
closing as won't do as nobody has worked on it, nor commented, nor voted
> Generalized solution for plugins to add secrets to source files
> ---------------------------------------------------------------
>
> Key: CB-11859
> URL: https://issues.apache.org/jira/browse/CB-11859
> Project: Apache Cordova
> Issue Type: New Feature
> Components: AllPlugins, cordova-cli
> Reporter: Shazron Abdullah
> Priority: Major
>
> i.e. set API keys and secrets that reside in source files in plugin.xml. Right now, this is a manual process.
> Usually these tokens are interspersed in with existing code, we could mandate a separate "secrets.h" (or equivalent) file that we can token replace to minimize search/replace errors.
> Either search/replace, or we "generate" a source file from these values. I like this latter approach better.
> So, the "before", which is included in the plugin:
> {code}
> // secrets.h
> // AUTO-GENERATED - do not modify!
> #define CLIENT_KEY @"NOT SET"
> #define CLIENT_SECRET @"NOT SET"
> {code}
> "After", according to `cordova plugin install` parameters:
> {code}
> // secrets.h
> // AUTO-GENERATED - do not modify!
> #define CLIENT_KEY @"ASGSKL888A"
> #define CLIENT_SECRET @"BobsYourUncle"
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org