Zanie Blue
Zanie Blue
That implementation is specific to 429's in order to respect the rate limit back-off headers. If feasible, it'd be good to reuse standard retry handling for httpx. I'm not sure...
@abrookins it'd be great to see this land on the roadmap as retries are important for handling service disruptions.
We can update the settings routes to handle secrets the same way we do for blocks now that we've added a workaround to our Pydantic models.
Unfortunately adding authentication is vastly more complicated than obfuscating our settings. For some users, that may be the preferred path though.
We are going to hide it, we just need to duplicate secret handling from blocks -> settings. If anyone is interested in taking that on, feel free to chime in....
See also https://github.com/PrefectHQ/prefect/issues/6086 If you could provide a MRE that would be very helpful. It's going to be hard for us to solve this issue without a reproducible example.
Thanks for sharing that. I believe all of the errors there should be resolved by #6730
> I believe that branch from https://github.com/PrefectHQ/prefect/pull/6730 shows that it is merged, so wouldn't this issue still exist? #6730 is merged but not yet released. It should be available tomorrow...
👍 I also hard a hard time finding it by searching — not sure what GitHub is up to there. Are you also seeing `Abort` in your tracebacks?
@samgarvis is this issue resolved for you?