Secrets in subflows

Core Development Feature Requests
1

Hi everyone,
I think a "secret" data type for subflow environment variables would be very useful for secrets, like API keys and other stuff you want to be stored encrypted in flows_cred.json file, like this:

image
image506Ă—548 13 KB

A default value for a secret environment variables may not make much sense, so it can have no input field in the subflow template. There should only be a secure-string field (like fields for passwords) in each subflow instance: every subflow instance will have its secret (or secrets, if many) stored in the flows_cred.json file instead of flows.json file.
You think this may be a thing in a future release?

1 Like
2

Yes. Support for a credential type of property is in 1.1.0

2 Likes
3

Great! Thank you

4

Are you thinking of releasing a new Beta for 1.1.0? I am developing a subflow now that could really benefit from a credential property but the current first Beta is a bit buggy for me to work with. Or possibly the full release is due any second now?

5

yes absolutely

6

Great, thanks. Though I am not sure which side of the 'OR' condition is going to be satisfied :slight_smile:

1 Like
7

Since both sides would be great, it doesn't really matter. :grinning:

2 Likes
8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.