FINERACT-2421: Refactor and secure GitHub Actions workflows#5890
Conversation
|
seems like need to fix security flaws raised by zizmor warning[dependabot-cooldown]: insufficient cooldown in Dependabot updates warning[dependabot-cooldown]: insufficient cooldown in Dependabot updates error[excessive-permissions]: overly broad permissions warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow warning[secrets-inherit]: secrets unconditionally inherited by called workflow error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion error[template-injection]: code injection via template expansion 149 findings (18 ignored, 97 suppressed, 14 fixable): 0 informational, 0 low, 21 medium, 13 high |
3d8b044 to
d6fb43f
Compare
|
@adamsaghy Ready for review can you review it again |
619b8a6 to
4c728cc
Compare
refactored reusable workflow configuration for GitHub Actions removed direct push triggers from reusable workflows and standardized workflow_call usage added and adjusted concurrency handling for CI workflows to manage redundant runs hardened workflow security by replacing inline GitHub context interpolation with environment variables in shell scripts added explicit secret declarations and removed secrets: inherit usage added persist-credentials: false to checkout steps across workflows updated workflow permissions and zizmor security analysis configuration added zizmor GitHub Actions security scanning workflow and related ignore rules fixed malformed workflow syntax and cleaned duplicate configuration lines updated Dependabot cooldown configuration for Maven and Docker updates
f0e6e69 to
049e1b8
Compare
|
@Aman-Mittal You can merge if you believe it is ready! ;) |
.github/workflows/zizmor.yml) to automatically scan workflow files for security vulnerabilities using zizmor.developwhenever files in.github/workflows/**are modified.medium, and disabling online audits.Description
Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Your assigned reviewer(s) will follow our guidelines for code reviews.