-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5/19/24 10:29, John Ralls wrote:
> No, the Alphavantage API Key preference sets ALPHAVANATGE_API_KEY in
> the environment. That’s why it would be easy to make more preferences
> with corresponding environment variables.
That is what I meant when I said I though that was how GC handled the
AlphaVantage key. Somewhere in the code I spotted
"bb:env['ALPHAVANTAGE_API_KEY'] = ...".
This is why I first asked about the possibility of adding more, and
mentioning a few modules requiring keys.
> Using environment variables seems clumsy to me, but having GnuCash
> include the keys in queries by hardcoding the source/key combinations
> couples versions of GnuCash and F::Q even more tightly than the
> hard-coded source lists do. At least with environment variables users
> can take advantage of new modules with API keys without having to
> wait for them to be incorporated into GnuCash as long as they learn
> how to set environment variables.
I believe for some users setting environment variables has been
problematic. But as you pointed out, the alternative of changing GC to
specifically mention source/key combos does present its own concerns.
In any case, a couple new modules requiring API keys are on the roadmap.
Plus a new currency rate module has been added in 1.62.
But now, time to relax for a spell.
Bruce S.
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQRzL0H5rBaeDPnpeL1IjAeprJFQBwUCZkpY7QAKCRBIjAeprJFQ
B75aAKDHsagQquzMSAbAhliVuxtgtcKn8gCeM06uW01+NWTkecJGobuZCmT8bow=
=4LWp
-----END PGP SIGNATURE-----
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
