Implement a logging system for all hfla github actions

[akibrhast]

Overview

As a member of the website team, we need a system that allows us to track GitHub action logs for an extended amount of time, beyond GitHub's 90 day allowance.

Action items

• Create some sort of system that allows logging of Github actions logs for an extended amount of time.
  • The logs should be stored in a .txt file in a directory called '/logs' which is added to .gitignore
  • The log needs to have a one to one correspondence with the GitHub actions logs. This means that all information logged by GitHub needs to also be logged in this system. (this includes time stamps and information about the triggers)
  • The only exception to the above is the code that is run. However, the name of the GitHub actions file should be in the log.

Resources/Instructions

If you have trouble starting this project, you might start with implementing the log with a GitHub action. The workflow_run trigger seems very promising if this is the route you want to take.

As this issue is fairly large, you might have a lot of trouble, so please reach out! Important things to keep in mind when designing this is that this is made for the team. Be conscious of how the logs are formed and formatted, so that they would be useful for the team! You might also want to improve upon the action items above (perhaps a way to clear the logs?). If you dare to challenge yourself, be sure to share that intention with the team! We love to hear your ideas.

Some useful links

Keeping your GitHub Actions and workflows secure: Preventing pwn requests
Events that trigger workflows
Workflow syntax for GitHub Actions
Storing workflow data as artifacts
GitHub GraphQL

[akibrhast]

To discuss with @Aveline-art

[Aveline-art]

Design/Research questions:

• Where and how will the information be stored?
• What ways are there to listen for the initiation or completion of a GitHub action?
• What information has to be part of the log?
• Who is the end user of the logging system?
• What does the current logging system lack that this needs to address? Answer: The current logging system only preserve logs for the last 3 months. It should preserve logs for over that amount.

Design criteria:
TBD.

[akibrhast]

Discussed with @Aveline-art and added details in the main body.

[ExperimentsInHonesty]

This issue needs a rewrite on the top, to be in the format of all our other issues

 ### Overview
 User story (as a ____ I need to do _____ for _____ reason)

### Action Items
- [ ] thing 1
- [ ] thing 2

### Resources/Instructions
Links that will be useful

[github-actions]

@Zak234 Please add update

1. Progress
2. Blockers
3. Availability
4. ETA

[Zak234]

Still working on the Github action. Experimenting with Javascript and Graph Ql. Available basically anytime. ETA, hopefully one week.

[Zak234]

Talked with Ava and it was decided that this issue should be closed due to its complexity and lack of benefits from completion. In case of being opened in the future, using REST API to download job logs seemed to be the most promising avenue although large amount of data processing would need to be done to remove the Github action code from the logs and get the data in a more readable state.

[ExperimentsInHonesty]

Wiki related to this issue https://github.com/hackforla/website/wiki/Decision-Records-on-Solutions-Not-Implemented