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
Respect PREFECT__CLOUD__SEND_FLOW_RUN_LOGS #6833
Conversation
Hm. Looking back at #4487 I do not think this setting is intended to be used this way. The engineer running the agent determines if flow run logs can be sent to Cloud. If I configure my agent not to send logs to Cloud, I would be pretty upset if any user could send logs by adding an environment variable. Perhaps we should allow this to be turned off per flow run but never turned on unless already allowed at the agent level. We'll want to check that this meets Recursion's requirements. As is, I think this could be seen as a security risk. |
Good point, I hadn't considered that.
We'll want to check that this meets Recursion's requirements. |
Yes, I think that agent having flow logs off should take precedence, but if the agent has flow logs on, it should be possible to turn it off at the flow run level. Updating the docs to communicate that clearly once implemented would also be great. |
Great! Definitely down for that implementation. @EmilRex you'll also need to implement this for all of the other agent types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you write tests covering our new expected behavior as well?
The
PREFECT__CLOUD__SEND_FLOW_RUN_LOGS
environment variables is ignored when explicitly set. This change avoids overwriting it with a default value when set.Closes #5521