The ECA module → is a current replacement for the old Rules module, and can replace a lot of custom code in a "no-code" way.
We are starting to use ECA more and more for integrations with 3rd party systems, doing direct posts to APIs. Moving the secrets into Key module would allow us to export these as recipes to use on other sites or post publicly.
There is currently no way to load a key value from an ECA model.
Create an ECA Action plugin that wraps the key retrieval service.
Determine where this plugin should live -- do you want it directly in the Key module? In a submodule? or a separate module entirely?
N/A
None.
None.
Active
4.0
Code
Regarding the question of where this plugin should live: My inclination is to include it in Key. What do other modules that provide ECA actions do?
I think Key module is the appropriate place for it. It is a plugin, so it can live really in any module -- was putting this out as a feeler for whether you'd accept it here.
Will work on this when I get a chance...