-
Notifications
You must be signed in to change notification settings - Fork 664
ci: 9879 inttest #1117
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
ci: 9879 inttest #1117
Conversation
DISCOVERY_URL: "https://api.us-south.discovery.watson.cloud.ibm.com" | ||
DISCOVERY_APIKEY: ${{ secrets.D1_APIKEY }} | ||
DISCOVERY_ENVIRONMENT_ID: ${{ secrets.D1_ENVIRONMENT_ID }} | ||
DISCOVERY_CONFIGURATION_ID: ${{ secrets.D1_CONFIGURATION_ID }} | ||
DISCOVERY_COLLECTION_ID1: ${{ secrets.D1_COLLECTION_ID1 }} | ||
DISCOVERY_COLLECTION_ID2: ${{ secrets.D1_COLLECTION_ID2 }} | ||
DISCOVERY_COLLECTION_ID3: ${{ secrets.D1_COLLECTION_ID3 }} # japanese | ||
|
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.
LGTM, my only question is if Discovery V2 uses its own set of credentials because I was under the impression that it did
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.
Your right, I need to fix this up. I will do that now and let you know if another review is needed. Thank you
🎉 This PR is included in version 6.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Add a GHA integration test workflow