Ryan Peden

I will add tests if we want to move ahead with these changes.

@anna-geller That message is what I'd expect when using an older agent since it's still running the old code. FWIW, I get the same thing when running a 2.4.2 agent...

@almemanuel you'll probably get more helpful answers on Prefect's Slack community, but I'll help however I can if you're still trying to solve this. The first thing I'd check for...

@tomasrollo There are two different S3 blocks - one is just called `S3` and the other is called `S3 Bucket`: `S3 Bucket` has a section for MinIO credentials. The catch...

@tomasrollo I should add that the reason you'd want to use `S3 Bucket` is that it accepts a MinIOCredentials block that lets you set the server URL. I hadn't realized...

@MrChadMWood the agent uses the same Docker image as everything else, so EXTRA_PIP_PACKAGES should work there, too. I'll give it a quick try and post an update if it works...

@MrChadMWood it was caused by the way I was overriding the entrypoint for the agent. I'll update it in the repo but this should make EXTRA_PIP_PACKAGES work: ``` ## Prefect...

@MrChadMWood, it looks like your `EXTRA_PIP_PACKAGES` entries use a colon instead of `=`. Does it work if you change ``` - EXTRA_PIP_PACKAGES:prefect-gitlab prefect-aws ``` to ``` - EXTRA_PIP_PACKAGES=prefect-gitlab prefect-aws ```...

It looks like GitLab was close to working. I'm not sure why it was timing out, but it might be that the `git clone` call that the GitLab Repository block...