SSWConsulting / SSWConsulting/SSW.Website
Visibility on secrets expiration
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Description:
We must avoid situations where our external endpoints could break due to any expiration of secrets or passwords without any visibility or notifications. Therefore, we must work with SysAdmins to cater to this problem in the future.
This particular problem caused huge issue for the enquiry forms failing silently.
Tasks:
- Reproduce the same bug by expiring or deleting the secret
- Add email notifications to SysAdmins prior to secret expiry
- HTML - Confirm we do not show any error on the client side + link to rule explaining why
- Investigate adding integration tests
- Investigate adding a health check for the website
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the failure by expiring or deleting the secret, then coordinate with SysAdmins on expiry notifications and inspect the website's client-side error behavior. Done means expiry visibility or email notification exists, client errors remain controlled, and the proposed integration tests or health check have been investigated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, nextjs
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100