Andrea
03/18/2023, 12:55 AM.env
file. If I do not define the configuration schema of the resource, something weird happens where the environment variable is not captured and instead the raw string is passed e.g. 'token': {'env': 'GCS_TOKEN'}
why does this happen? Setting a configuration schema should not affect whether environment variables are collected, right? I want to have a resource with a dynamic schema with some user-provided parameters coming from the environment. Is this a bug?