New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate restart policy into the container object #4160
Conversation
c3f6b64
to
5514c22
Compare
{ | ||
name: "enabled restart policy", | ||
container: &Container{ | ||
RestartPolicy: &restart.RestartPolicy{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, do we/are there plans to validate RestartPolicy isn't empty if restart policy is enabled when we receive the task payload?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good question, we may want to validate that when we initialize the restart trackers, let me sync with Fargate dataplane on how we want to do that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 thanks Cam! I also have no issues for this to be a follow up
Summary
go mod vendor
in the agent/ dir to pull in ecs-agent/ shared lib changes.Exact struct naming is still subject to change but this should roughly match the GA feature.
Testing
New tests cover the changes:
Description for the changelog
NA
Does this PR include breaking model changes? If so, Have you added transformation functions?
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.