Definitive plan for cruft

[kjaymiller]

Our cruft plan has hit a snag due to Microsoft org security settings, preventing GH Actions to create PRs.

FMI - https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token.

Option 1: Manually run cruft update as a pre-commit hook?

Pros

• Would check for updates and raise alarm when things aren't in sync

Cons

• Adds pre-commit which would call for some other configuration changes.
• Doesn't auto-update

Option 2: Create Repo, Update, and commit

Pros

• Does EVERYTHING but submit the PR

Cons

• Ran into some issues trying to deploy
• Many of the checks are on PR and not push
  • This could be changed

Option 3: Manually Update each one

Pros

• Works Every time

Cons

• Potential drift if repos are missed

[kjaymiller]

Update

Option 2 Wins, but there are some minor exceptions.

We aren't able to run cruft via workflow when modifying a GitHub Action so we can create a script that lives in cookiecutter-relelcloud/tools that does the following.

Iterates through combinations:

• Creates a Placeholder Folder
• Attempts to pull the combination url
• Runs Cruft to update based on the path's cruft.json
• Creates pull request for the updates