-
Notifications
You must be signed in to change notification settings - Fork 948
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
secret() function seems inconsistent with sourcing secrets #5661
Comments
It must be an issue in the OpenAI plugin, we'll investigate, thx for the report! 👍 if you see it with any other plugin, keep us posted. we're working on making all properties dynamic (without losing strong typing) in the next release so this should get better soon |
Well I actually do have a couple more very similar issues that I'll outline here for documentation's sake NextcloudTesting simple nextcloud integration to download (and then eventually also upload) a file I was not able to pass my credentials to my python script
And in my
I can see that these are set but masked in the logs - and I also tried to print them from the pyton script but they were
In this case the python error is |
I also had issues with a terraform workflow but I kind of stupidely removed the docker volume and didn't back that workflow up so I don't have it or the log immediately handy... the issue was with setting up an s3 provider for remote state storage. I wanted to use my minio instance and that's compatible with the aws cli/boto sdk with passing the AWS secrets, just like in the first post, into the environment - then But I could never get the terraform flow to get through If a flow and logs would be really valuable I can try to recreate this in the next few days |
Describe the issue
I can sucesfully run 1 flow but another very similar one fails. It looks to me to be an issue with passing a secret down because if I hardcode the values in my flows/scripts then they work fine.
Successful flow
I can create a bucket just fine on my minio instance
I have a
.env_encoded
like the docs say, it looks like thisI
docker compose up -d
and make a flowthis runs great
Failure
In the same encoded env file I have
Then the flow that failes
When I run this the error is that I didn't supply an apiKey, but if I hardcode it in the flow then it works
Environment
The text was updated successfully, but these errors were encountered: