Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: expose database upgrade logs to end-users #27924

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

feat: expose database upgrade logs to end-users #27924

wants to merge 4 commits into from

Conversation

pcnc
Copy link
Member

@pcnc pcnc commented Jul 11, 2024 •
edited
Loading

I have read the CONTRIBUTING.md file.

YES

What kind of change does this PR introduce?

  • Ability for users to browse logs related to their database upgrade operations, providing a way to troubleshoot failed upgrades
  • Introduces a new Database Operations sub-category in the logs page
    • Currently serves database upgrade logs, will serve restore failure logs etc
    • Meant to display logs for one-off/not regularly occurring operations separately from product/service logs
  • Enhances the upgrade failure banner by providing a link to the exact time interval when the upgrade took place
  • Fixes the hour displayed in the upgrade failure banner
    • Was displayed as being in UTC, whereas dayjs converted it into local time
    • Removed UTC as it's more relevant to the end-user to know when it took place in their local time
  • Fixes Initiated At time actually displaying failure time
    • Depends on an API change reaching prod

Additional context

  • Currently blocked by:
    • Pending API changes
    • Pending log shipping changes
  • Any feedback (especially regarding naming) is more than welcome

What is the new behavior?

image image

Add any other context or screenshots.

@vercel Vercel
Copy link

vercel bot commented Jul 11, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
design-system ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2024 1:54pm
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2024 1:54pm
studio-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2024 1:54pm
zone-www-dot-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2024 1:54pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
studio ⬜️ Ignored (Inspect) Visit Preview Aug 6, 2024 1:54pm
studio-self-hosted ⬜️ Ignored (Inspect) Visit Preview Aug 6, 2024 1:54pm

@supabase Supabase
Copy link

supabase bot commented Jul 11, 2024

No changes detected in supabase directory.
This pull request has been ignored for the connected project xguihxuzqibwxjnimxev due to its connection settings.
Go to Project Integrations Settings ↗︎ in order to change this behavior.

Branching Preview Branches by Supabase.
Learn more about Supabase for Git ↗︎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@pcnc