-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
fix: docker ephemeral environment, push only on testenv comment #26473
fix: docker ephemeral environment, push only on testenv comment #26473
Conversation
/testenv |
1 similar comment
/testenv |
/testenv up |
@dpgaspar Ephemeral environment creation is currently limited to committers. |
Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
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.
Looks good!
Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
const artifacts = await github.actions.listWorkflowRunArtifacts({ | ||
owner: context.repo.owner, | ||
repo: context.repo.repo, | ||
run_id: ${{ github.event.workflow_run.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.
hey @dpgaspar this change broke the ephemeral envs because the context is different. Before the trigger was a workflow_run, and now being comment created this property is not available in this context.
…he#26473) Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
…he#26473) Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
…he#26473) Co-authored-by: Geido <60598000+geido@users.noreply.github.com>
SUMMARY
Currently docker ephemeral env (https://github.com/apache/superset/blob/master/.github/workflows/docker-ephemeral-env.yml) triggers when docker workflow finishes, this changes moves this step to when an actual committer requests for a docker env to be created. Both workflows triggers have
secrets
access butissue_comment
uses current default branch commit SHA so it's no subject to PR changes and validates that only privilege users can execute this step.I was not able to properly test this change since it run with current master git SHA, so I expect that further changes may be needed.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION