Hi <@U01PXUT0XGD>! Unfortunately, it seems like yo...
# prefect-server
k
Hi @Joe McDonald! Unfortunately, it seems like you’re right that there is no way to pass botocore_config yet through the CLI.
j
@Kevin Kho do you think it would be prefered to just see if AWS_MAX_ATTEMPTS OR AWS_RETRY_MODE are set as environment variables or to read a file like done for kwargs?
z
The
Config
that we are loading there should not override values that you set otherwise (aka via the AWS config or env variables)
j
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#using-the-config-object
Copy code
As described earlier, there are options used here that will supersede those found in other configuration locations
z
Is it overriding the strategy? There's a check before it is set to see if it already has a value
j
So you initialize a blank
Config
since from CLI I can’t load botocore_config, then since it is blank there is no retry mode, so it sets it to
standard
. I want it set to
adaptive
z
I see. Passing these things from the CLI is pretty hard because AWS wants specific python types for each parameter. Instead, I've added this fix https://github.com/PrefectHQ/prefect/pull/4417
You can also easily initialize your
ECSAgent
from a python file and just call
.start()
which is all the CLI does.https://github.com/PrefectHQ/prefect/blob/faf7f57e88f51fab5aca8d1a674566ee2afc39f1/src/prefect/cli/agent.py#L88
j
Right now we are using the prefect docker container in ECS and have been trying to avoid having to roll our own so that we can update easy from docker hub just changing version number and everything is being passed in via environment and cmd
That was the other option since the only setting that is being overridden is the retry mode, your PR is exactly what I needed.