Currently the default API key used in the agl-service-weather is one of the developer. Likely should be one controlled by AGL so can upgrade subscriber API accesses in the future.
Environment
None
Activity
Jan-Simon Moeller
May 14, 2019 at 1:54 PM
No good idea to be honest. We can only replace it with 'another' developer key and expose a setting/var in the recipe to replace it with another. IMHO best we can do.
Matt Ranostay
April 17, 2019 at 5:50 PM
It is a key under my personal email.
Also one can change the key now.. but it is stored in the data persistence binding. Ideally we probably want to figure how to do this as a build option, thoughts?
Jan-Simon Moeller
April 15, 2019 at 2:52 PM
What key is in now ? We should expose that somehow so users can easily replace it.
AGL demo code can stay on a free key.
For CES we might either get a 2nd free key or then deploy a dedicated key.
Currently the default API key used in the agl-service-weather is one of the developer. Likely should be one controlled by AGL so can upgrade subscriber API accesses in the future.