Indeed a key wasn’t the best of the examples as it should be separated from code.
But I didn’t mean to say that the key should be hard-coded in the module.
Say I want to set it to a specific ENV variable. I can think of some providers that don’t let you chose the env variable where they store some piece of data.
Just seing how core modules can use the options object from the SC step I thought that maybe it was possible to read from a custom route. But of course, custom modules wouldn’t generate a SC core json file.
"steps": [
"s3/scaleway",
{
"name": "sign",
"module": "s3",
"action": "signUploadUrl",
"options": {
"provider": "scaleway",
"bucket": "",
"key": "{{$_ENV.NODE_ENV+'/img/user/'+$_SESSION.security1Id+'/profile/profile.jpeg'}}",
"acl": "public-read"
},
"outputType": "text",
"output": false
},
Potentially I could write a json file from the custom module with the configuration and then read it from the custom route, right? Same as with security providers, connection and S3 providers. Please correct me If I am making wrong assumptions.