Add config validation utility to Fargate Agent #2768
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for contributing to Prefect!
Please describe your work and make sure your PR:
changes/
directory (if appropriate)docs/outline.toml
for API reference docs (if appropriate)Note that your PR will not be reviewed unless all three boxes are checked.
What does this PR change?
This PR adds a function to the fargate agent for validating the configuration that it was provided. For example something like this could happen:
And this
validate_configuration
function will test to see if the agent has the proper setup to register a task definition and run the task.Why is this PR important?
It is not uncommon for questions around the fargate agent to be based around configuration and usually these are only discovered after getting it up and running. This can hopefully alleviate some issues before attempting to run a flow by validating ahead of time.
I'm also now thinking that maybe every agent should have its own
validate_configuration
to verify that it is configured properly.