-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Run integration tests in multiple aws partitions #9342
Comments
Hi @jmcarp Thanks for letting us know about this - we are indeed trying to get this setup! We are trying to get an account in US-Gov to help us run our tests in. Lots more work is going to happen in this work over the coming weeks as we are overhauling our acceptance tests :) Please keep an eye for the announcements - hopefully we will catch these types of issues going forward Paul |
@stack72 Did y'all find a way to run your tests in GovCloud? If not, I'd like to discuss running them for you in our account as we use terraform daily and frequently run into GovCloud specific issues. Thoughts? |
Hi @cnelson We have been able to run selective tests in GovCloud - the issue with running them all is that we will get a lot of failures due to unsupported features Paul |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I don't know this for a fact, but I'm guessing that aws integration tests are only run in the default "aws" partition. I'm guessing this because I recently fixed some (but likely not all) partition-related bugs in #9273. Ideally, integration tests would run in at least two aws partitions so that bugs of this kind would be caught automatically. It sounds like getting an account in the aws-us-gov partition can be complicated, so testing in the aws and aws-cn partitions might be the simplest path.
I would send a patch for this myself, but I'm not sure where the acceptance tests run--I don't see them in travis and am guessing you all have a private ci service for this?
The text was updated successfully, but these errors were encountered: