-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pablo/dev 177 add pipeline check method to sdk #19
Pablo/dev 177 add pipeline check method to sdk #19
Conversation
PIPELINE_ID: ${{ secrets.PIPELINE_ID }} | ||
PIPELINE_ACCESS_TOKEN: ${{ secrets.PIPELINE_ACCESS_TOKEN }} |
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.
It doesn't seem right.
At least, let's rename it into something more concrete, like INTEGRATION_TESTS_PIPELINE_ID
.
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.
Base URL also needs to be configured - we shouldn't run integration tests on production environment.
At least, it could be staging
.
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.
But anyway, conceptually we need to do integration tests differently.
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.
Good points! We can rename the secrets.
As for the environment, agree, we should test on a staging environment.
is_access_token_valid
toPipelineClient
to return True if the access token is valid, False otherwise