Is there a clean way to store JSON config data for use across multiple workflows?

1

This topic was automatically generated from Slack. You can find the original thread here.

Nacho Caballero : Besides using it for API keys, I’ve been using PD’s environmental variables to store JSON data that multiple workflows need to access. I’m wondering if anyone has any recommendations for a cleaner alternative. Maybe some kind of cloud NoSQL DB? (probably overkill) or a .json file in Google Drive (seems hacky)

2

Giao Phan : Would it help if you could share workflow attachments across workflows?

3

Nacho Caballero : It would if the attachment could be a JSON file and I could edit it within PD. If I have to download it, edit it and upload it every time, I don’t think that would work

4

Elton Morais : I’m using it too. What I want is just an editor that shows hints/errors for JSON. Just like the checkpoint editor…

5

Jay Vercellone : Perhaps having an action that returns static data?