-
Notifications
You must be signed in to change notification settings - Fork 278
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
Update gradle check jenkins to add Azure and GCP account for OpenSearch repository tests #2386
Comments
Basically, if I get hit by a bus/win the lotto, I don't want to be the only person with these passwords. Whaddya think, @peterzhuamazon? |
Hi @dreamer-89, Thanks! |
Hi @gaiksaya, Thanks for getting back on this. I need to export access key/secret keys for Azure & GCP accounts we recently created. Yes, these needs to be added to jenkins environment so gradle job can use same. The accounts are already created for Azure, GCP. Right now, I need to do a quick verify that exporting creds let gradle check job run integration tests against these external cloud. I will update once I do that, post that we can proceed with adding creds on jenkins script. |
@dreamer-89 Whats the status of this issue? |
@bbarani : Thanks for checking on this and apologies for losing track on this. This needs a quick POC on our end to verify that repository integration tests uses external Azure/GCP end-points when valid repository creds are provided. This work is still pending. I will surface this in the team meeting to get prioritization on this task. Once this is completed we can update the jenkins job. CC: @anasalkouz |
Closing this issue for as stale. Please feel free to re-open or create new one once work is done from OpenSearch's end. |
Description
Today, Opensearch engine mocks external cloud providers for running repository-[azure/gcp] integration tests. As part of this issue, we need to add creds for azure/gcp accounts so that engine can run integration tests against these cloud providers.
Related
opensearch-project/OpenSearch#3362
opensearch-project/OpenSearch#1763
The text was updated successfully, but these errors were encountered: