fix: take into consideration the DesiredCount/RunningCount for resource readiness #2023
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.
Currently, ECS Service resource is only taken into consideration the
.Status
field to decide on the readiness of the Crossplane resource.I think this is an overlook, and Crossplane should also take into consideration the
DesiredCount/RunningCount
, since it is part of the input Spec. Returning ready based only on the.Status
might result in returning to the client a ready state when in fact, no tasks are running yet.Before wrapping up the PR with tests, I would like to get some feedback from you to undertstand if you agree with this change or not.
I have:
make reviewable test
to ensure this PR is ready for review.Thanks.