-
Notifications
You must be signed in to change notification settings - Fork 27
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
smoke_test: Fix Failure on Windows GitHub Workflow #571
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,7 +32,7 @@ on: | |
description: "Choose OPA version" | ||
required: true | ||
type: string | ||
default: "v0.60.0" | ||
default: "v1.0.0" | ||
|
||
jobs: | ||
configuration: | ||
|
@@ -53,9 +53,9 @@ jobs: | |
|
||
# Default values for other events | ||
else | ||
operatingsystem_val="['macos-latest']" | ||
operatingsystem_val="['windows-latest', 'macos-latest']" | ||
pythonversion_val="['3.10']" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Other than in DownloadAndInstall.md where we indicate "v3.9 or higher", I don't see any references to a definitive minimum supported python version in the code. Recommend we move this out of the workflow in favor of a more maintainable location that doesn't require a code change when we decide to bump to v3.11, etc. Setting a GitHub secret as "MIN_PYTHON_VERSION"="3.10" may be a short-term alternative. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Support for Python 3.9 is dropping as of October this year, and we have another year for 3.10. I didn’t change the Python version used for this workflow (3.10). I think it’s a reasonable version to test with, considering 3.9 is going away. We can always look at other ways to have the workflow get the Python version to use. This PR is specific to the smoke test not working on Windows, and the issue is resolved with this PR. |
||
opaversion_val="0.60.0" | ||
opaversion_val="v1.0.0" | ||
fi | ||
echo "operating-system=$operatingsystem_val" >> "$GITHUB_OUTPUT" | ||
echo "python-version=$pythonversion_val" >> "$GITHUB_OUTPUT" | ||
|
@@ -106,4 +106,6 @@ jobs: | |
json: ${{ secrets.GWS_GITHUB_AUTOMATION_CREDS }} | ||
|
||
- name: Run ScubaGoggles and check for correct output | ||
run: pytest ./scubagoggles/Testing/Functional/SmokeTests/ -vvv --subjectemail="${{ secrets.GWS_SUBJECT_EMAIL }}" --customerdomain="${{ secrets.GWS_DOMAIN }}" | ||
run: | | ||
${{ env.SCUBAGOGGLES_ACTIVATE_VENV }} | ||
pytest ./scubagoggles/Testing/Functional/SmokeTests/ -vvv --subjectemail="${{ secrets.GWS_SUBJECT_EMAIL }}" --customerdomain="${{ secrets.GWS_DOMAIN }}" |
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.
Recommend we pull in the latest OPA version rather than having to manually update default version of the input variable if we want latest. Then make this input optional but override the default if there's a diff.
OPA v1.0.0 is already out of date as OPA did a patch release to [OPA v1.0.1[(https://github.com/open-policy-agent/opa/releases/tag/v1.0.1) to address Go CVEs.
I did something similar on the ScubaGear side to check for latest OPA version updates
Bash equivalent
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.
This workflow now uses the latest OPA version, although this wasn’t the target of the PR/issue.