cloudposse / github-action-atmos-component-updater Goto Github PK

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature

The component updater creates and orphans a lot of branches. Any PR that is not merged and is closed creates a stale branch.

Add an (optional) step to the component updater workflow to clean up stale branches

Expected Behavior

The component updater should include an option to regularly clean up stale branches in the same workflow

Use Case

Clean up stale branches every night

Describe Ideal Solution

No persistent stale branches created by this action

Alternatives Considered

Use another tool on a schedule to clean up stale branches. Examples

• https://github.com/beatlabs/delete-old-branches-action
• https://github.com/marketplace/actions/stale-branches
• many more from googling

Additional Context

n/a

Right now action before it run needs to build itself, which not only waste time and resources but can be affected by Network issues and so on, which can break workflow before it starts any cheks.

In the metadata, provide a list of what components have also been affected to hint at other dependencies.

Embed the release notes in a <details/> block for the current release. Bonos points for aggregating all release notes between versions.

Describe the Bug

Submodule modules/postgresql-user is not updated within aurora-postgres-resources.
The line

Expected Behavior

Changes in a submodule only should be detected by the updater.

Steps to Reproduce

Steps to reproduce the behavior:

1. Configure component.yaml with version 1.310.0
2. I expect to get version 1.330.0
3. Updater say that no changes are detected.

Screenshots

2023-10-26T10:19:11.1443389Z [26-10-2023 10:19:11] INFO    Processing component: aurora-postgres-resources
2023-10-26T10:19:11.6096994Z [26-10-2023 10:19:11] INFO    Looking for PR with branch: component-update/aurora-postgres-resources/1.330.0
2023-10-26T10:19:12.0148588Z [26-10-2023 10:19:12] INFO    Executing 'atmos vendor pull -c aurora-postgres-resources' for component version '1.310.0' ... 
2023-10-26T10:19:15.0423445Z [26-10-2023 10:19:15] INFO    Successfully vendored component: aurora-postgres-resources
2023-10-26T10:19:15.0428870Z [26-10-2023 10:19:15] INFO    Executing 'atmos vendor pull -c aurora-postgres-resources' for component version '1.330.0' ... 
2023-10-26T10:19:18.2087857Z [26-10-2023 10:19:18] INFO    Successfully vendored component: aurora-postgres-resources
2023-10-26T10:19:18.2125023Z [26-10-2023 10:19:18] INFO    Looking good. No changes found

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• github action