@Glime is it possible to extend

secret_requests

using

Task.with_overrides()

?

Based on the provided context, there is no direct mention or example of extending

secret_requests

using

Task.with_overrides()

. The discussions and documentation primarily focus on the use of

secret_requests

in tasks and workflows, including how to specify secrets for tasks and how these secrets are injected into tasks. However, there is mention of using

with_overrides

for other purposes, such as modifying task resources or configurations, but not specifically for extending

secret_requests

. For instance, in the context from GitHub issue #4957,

with_overrides()

is discussed in the context of resource allocation, not secret management. Similarly, GitHub issue #4067 mentions

with_overrides

for repurposing a task within the same workflow but does not discuss extending

secret_requests

. Therefore, based on the provided context, it cannot be conclusively stated that

secret_requests

can be extended using

Task.with_overrides()

. For such functionality, it might be necessary to directly specify

secret_requests

within the task definition or explore other mechanisms within Flyte for managing secrets. For the most accurate and up-to-date information, it's recommended to consult the official Flyte documentation or reach out to the Flyte community for guidance on extending

secret_requests

using

Task.with_overrides()

or alternative methods for managing secrets in tasks.