feat: CI pipeline targeted apply — module-aware plan and apply #211
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-platform!211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "198-ci-targeted-apply"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
tofu planandtofu applyto the Woodpecker CI pipelineterraform/modules/X/files change, the pipeline runs-target=module.Xinstead of a full plan/applyChanges
.woodpecker.yaml— clone step: increased fetch depth from 1 to 2 soHEAD~1is available for push-event diffing.woodpecker.yaml— plan step: added module detection block that diffs PR branch against target branch, extracts changed module names, builds-target=module.Xarguments; PR comment now indicates targeted vs full with module list.woodpecker.yaml— apply step: added same module detection logic usingHEAD~1..HEADdiff, builds targeted apply command, preserves lock retry for both targeted and full paths.woodpecker.yaml— apply step: fixed inconsistent$vs$$escaping in lock retry block (Woodpecker requires$$for literal$)Test Plan
terraform/modules/monitoring/— verify plan comment says "targeted: monitoring"terraform/main.tf— verify plan comment says "full"Review Checklist
Related Notes
project-pal-e-platform