#I think the last remaining bits are
1 messages · Page 1 of 1 (latest)
Was just working on that, I added a plaintext resolver to the secret object
I know we were trying to avoid adding as much as possible to secret api for now, but I don't see any other reasonable way
We could have extensions mount the secret into an exec and then cat the secret value, getting it over stdout
But that obviously defeats the purpose 🙂
yep. I know there's secrets API discussions and TBD's going around, but we'll need something for now to get unstuck
We also could use the same thing we do with mounts where they get automatically mounted into the extension container, except automatically turn secret inputs into env vars. But I really don't want to keep adding to that hack until we've cleaned it up more; the way it finds those types is too fragile and easy to break right now.