♻️ Refactor SSW Rules Widget

[JackDevAU]

Cc: @bradystroud @babakamyljanovssw @adamcogan

Hi Team,

Pain

Our current SSW Rules Widget relies on Azure Functions and a CosmosDB table, which adds unnecessary complexity and maintenance overhead to our system. The current issues we are facing is due to the builds and Azure Functions being out of sync and not storing all the data required.

What code could be improved?

• The SSW Rules Widget codebase, specifically the parts that interact with Azure Functions to fetch rules.
• A Single consistent retrieval method(s) that return the latest Rules information. Function is used and exported from the widget and used inside Rules + Widget.

Acceptance Criteria

• Add new fields title, uri, isArchived to history.json
• Refactor to use the history.json api instead of the Azure Functions
• Remove all Azure Functions previously used for fetching rules
• Remove the unnecessary table from CosmosDB
• Ensure all existing functionality is maintained
• Update documentation to reflect new architecture
• Performance benchmarks show no degradation
• Implement GitHub API integration to fetch GitHub user information
• All tests pass, including new tests for GitHub API integration
• Implement caching mechanism to optimise GitHub API calls (optional - might not be needed)

More Information

• We'll need GitHub API credentials or tokens for authentication
• Consider implementing a fallback mechanism in case of GitHub API unavailability
• Ensure rate limiting considerations are accounted for in the new implementation

Screenshots

Figure: Current Widget Architecture Flow

Figure: Planned Widget Architecture Flow

Thanks!

[babakamyljanovssw]

Update

PRs drafted to add new fields to history.json

SSWConsulting/SSW.Rules.Functions#59
#1440

[babakamyljanovssw]

Update:

There were some blockers due workflows were failing for SSW.Rules and SSW.Rules.Functions projects.

New Issues are created and PRs to resolve these blockers:

Issues:

• 🐛 Bug - "Gatsby Build" job is failing due to whitespace issues #1448
• ❌ Deprecated actions/ packages SSW.Rules.Functions#65

PRs:

• Remove space - failing build SSW.Rules.Content#9142
• XS✔ ◾ Fix filename long issue SSW.Rules.Content#9143
• update deprecated action package SSW.Rules.Functions#61
• Update packages 2 SSW.Rules.Functions#62
• Update release.yml SSW.Rules.Functions#63
• Fix functions deployment SSW.Rules.Functions#64

[babakamyljanovssw]

Update:

Drafted PR on SSW.Rules.Widget repo to refactor so it uses history.json and commits.json

SSWConsulting/SSW.Rules.Widget#55

[babakamyljanovssw]

Update:

PRs to update widget version for SSW.Rules and SSW.People projects

• ♻️ Updated widget package to new version #1449
• ♻️ Updated widget package to new version SSW.People#677

[babakamyljanovssw]

cc: @bradystroud @JackDevAU

Update:

We are going to wait for 1 week and then proceed with removing unnecessary tables from CosmosDB

[babakamyljanovssw]

Update:

Drafted PR to remove unused Azure Functions for widget and entity context

SSWConsulting/SSW.Rules.Functions#83

[babakamyljanovssw]

Update:

The UpdateLatestRules functions wasn't being used after last time I checked which is good and can be removed safely, but the GetLatestRules function was called a few times.

Figure: A few calls made to function after last check

Not sure where it is being called from, this function was being used in widget, but we have updated widget to new version to use history.json.

I checked the request logs for this function before widget upgrade and after widget upgrade for the 7 day period:

• 1400 logs are returned before widget upgrade
• 7 logs are returned after widget upgrade

Currently investigating where these calls are made from

[babakamyljanovssw]

Update

I couldn't find from where the GetLatestRules are being called yet. The calls are not frequent as it is used to be after recent changes to widget's data source. Currently I'm working on #1448 as top priority.

This work still in progress

[babakamyljanovssw]

✅ GetLatestRules and UpdateLatestRules functions were removed

[babakamyljanovssw]

Implement GitHub API integration to fetch GitHub user information

All tests pass, including new tests for GitHub API integration

Implement caching mechanism to optimize GitHub API calls (optional - might not be needed)

All above tasks are not required, as we don't need to call GitHub API to get user info because commits.json already has user information and widget is using it to get latest rules updated by specified user.
For more info look at this PR - SSWConsulting/SSW.Rules.Widget#55

[babakamyljanovssw]

✅ Done - removed LatestRules container from cosmos db

Figure: current cosmos db containers