🐛 Bug - Rule metadata (author and last updated date) not visible on rule pages

[griffenedge]

Requested by: @griffenedge via YakShaver.ai 🦬
cc: @griffenedge, @tiagov8, @adamcogan, @Marxoz, @PothieuG, @Freego1783, @Calinator444, @edkranz, @wicksipedia

Hi Team!

  🟥  Watch the video (1 min 2 sec)

  Url from screen share: https://www.ssw.com.au/rules/consistent-ai-generated-characters

Pain

When viewing rules in Rules V3 (TinaCMS), the metadata showing the author and the last updated date is missing. Currently, only the 'View History' link appears below the rule title. This issue occurs across all tested rules and prevents users from easily identifying rule ownership and recency.

Acceptance Criteria

1. Author metadata is visible on each rule page.
2. Last updated date is visible on each rule page.
3. Metadata is displayed consistently below the rule title, alongside or near the history link.
4. Metadata is visible for all existing and newly created rules.
5. No regression to rule history functionality.

Reproduce Steps

1. Navigate to Rules V3 (TinaCMS).
2. Open any existing rule (e.g. as shown on Griffin Edge’s screen recording).
3. Observe the area below the rule title.
4. Confirm that only the 'View History' link is visible and author/last updated metadata is missing.

Screenshot

Figure: Rule pages missing author and last updated metadata

[PothieuG]

Hey @griffenedge ,

I could not reproduce this bug.
Can you check again please ?

Here are the url of the YakShave:

• https://www.ssw.com.au/rules/how-to-generate-an-ai-image
• https://www.ssw.com.au/rules/consistent-ai-generated-characters

[PothieuG]

With @Aibono1225 we tried to check if it could be related to GitHub Rate API but it doesn't seems to be related to.
I sent a message to SysAdmin to check with them if they can have more information about SSW organization GitHub API calls and limits. See if we can pull something from that.

[griffenedge]

Hey @PothieuG, I'm pulling in @edkranz, @jakebayliss, @Calinator444, and @wicksipedia who were pulled in immediately after this YakShave was recorded, and from memory had some theories on what was happening.

[Calinator444]

Hey @griffenedge, @griffenedge, @jakebayliss, @wicksipedia,

I was looking into this on Friday. Sorry, I didn't realise we had an issue tracking this.

The actual cause based on my investigation is that our app service deployment settings are being wiped at the beginning each time a new deployment is created for SSW Rules, including the private key that we're using to sign requests to GitHub. I know this is true because I checked the environment variables on our app service with @chrisschultzssw on Friday.

The author metadata isn't displaying because the private key used to sign requests to GitHub's history API (which we use to populate the "last updated" section) can't be signed. The key gets wiped along with the other deployment settings for our app service at the beginning of each deployment.

Solution

We're currently redeploying the app service for SSW Rules at the beginning of our deployment workflow along with the rest of our infrastructure. This is causing the environment variables to be erased for the running app service.

Option A: (Recommended) Instead of redeploying our app service each time we deploy, we could move the infrastructure deployment to a separate GitHub action which would not be re-run for code changes, only when we need to fully redeploy our infrastructure. Then we could use deployment slots in Azure to swap out deployments for SSW Rules with the latest build instead.

Option B: We could set the environment variables for the app service at the beginning of the current deployment instead of at the end, meaning the app service would always have access to the latest environment variables and wouldn't need to wait for a full build. This approach is risky because it still effects production before the build completes.