-
Notifications
You must be signed in to change notification settings - Fork 132
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
Reference TaskDefinition ARN if resolvable #1028
Conversation
Continue of #826 (comment) |
/test-examples="examples/ecs/service.yaml" |
Thanks for the contribution, @mhoshi-vm! This looks like a better approach than the one you used in the previous PR. There's a problem with the end-to-end tests. The import step, which is intended to validate that the resource remains stable when e.g. the provider pod dies, is failing because of an issue with the ecs cluster resource:
My best guess is this is another example of something I've seen often with the terraform aws provider. Sometimes the value of the It looks like both ecs cluster and ecs service have their external name configurations overwritten in Problematically, the custom GetExternalNameFn throws an error when the terraform id is not in the expected format, which the import test (which did not exist in May of 2022 when that custom name was committed) shows us happens frequently. So I think we should fix that. Based on my reading, I'd try just using To get setup to run the e2e tests locally, all you need to do is follow the directions in the makefile to set the UPTEST_CLOUD_CREDENTIALS env var (you can just set credentials for |
Not sure why the lint gone into error, but I hope i done this correctly ... |
/test-examples="examples/ecs/service.yaml" |
@mhoshi-vm You'll need to remove the manual-intervention annotation on the Service in |
/test-examples="examples/ecs/service.yaml" |
Failed with the following. Trying to resolve
|
/test-examples="examples/ecs/service.yaml" |
@mbbush i think i passed all the tests, please review |
/test-examples="examples/ecs/service-static-cluster.yaml" |
a4ddcfa
to
fdae02e
Compare
/test-examples="examples/ecs/service.yaml" |
This provider repo does not have enough maintainers to address every pull request. Since there has been no activity in the last 90 days it is now marked as |
This pull request is being closed since there has been no activity for 14 days since marking it as |
Description of your changes
Re-Fix idea for #585
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Run this code locally and checked the service to run more than the interval.