You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The run_smoke_test.yml workflow runs when pull requests are opened/synchronized and on pushes to main. After the initial PR is merged, we can expand the workflow_dispatch functionality to accommodate user input.
Motivation and context
One drawback with the current implementation is hardcoded values in the workflow. The workflow would be more dynamic if a user can specify comma-delimited values for the os, python version, and opa version for further testing.
Implementation notes
Add inputs under workflow_dispatch, which can be accessed in the workflow with ${{ inputs.name }}. Below is an example from one of ScubaGear's workflows:
on:
workflow_dispatch:
inputs:
OverrideModuleVersion:
description: "Always enter the release version in semantic version format, Major.Minor.Patch (e.g., 1.3.0):"
required: false
type: string
IsPrerelease:
description: "If pre-release, check here:"
required: false
type: boolean
default: false
Acceptance criteria
How do we know when this work is done?
run_smoke_test.yml can be run manually with custom user input for os, python/opa versions. Otherwise use default values.
The text was updated successfully, but these errors were encountered:
💡 Summary
The run_smoke_test.yml workflow runs when pull requests are opened/synchronized and on pushes to main. After the initial PR is merged, we can expand the workflow_dispatch functionality to accommodate user input.
Motivation and context
One drawback with the current implementation is hardcoded values in the workflow. The workflow would be more dynamic if a user can specify comma-delimited values for the os, python version, and opa version for further testing.
Implementation notes
Add inputs under workflow_dispatch, which can be accessed in the workflow with ${{ inputs.name }}. Below is an example from one of ScubaGear's workflows:
Acceptance criteria
How do we know when this work is done?
The text was updated successfully, but these errors were encountered: