Skip to content

[db] add migration to alter pat table allow null expirationTime #19328

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.

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

Closed
wants to merge 2 commits into from

Conversation

mustard-mh
Copy link
Contributor

Description

DB migration part of #19327, split in case we need to do revert / rollback

Related Issue(s)

Relates EXP-1084

How to test

Should be tested in #19327

Documentation

Preview status

gitpod:summary

Build Options

Build
  • /werft with-werft
    Run the build with werft instead of GHA
  • leeway-no-cache
  • /werft no-test
    Run Leeway with --dont-test
Publish
  • /werft publish-to-npm
  • /werft publish-to-jb-marketplace
Installer
  • analytics=segment
  • with-dedicated-emulation
  • workspace-feature-flags
    Add desired feature flags to the end of the line above, space separated
Preview Environment / Integration Tests
  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-gce-vm
    If enabled this will create the environment on GCE infra
  • /werft preemptible
    Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
  • with-integration-tests=all
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
  • with-monitoring

/hold

@mustard-mh mustard-mh marked this pull request as ready for review January 16, 2024 19:22
@@ -53,7 +53,7 @@ export class DBPersonalAccessToken {
scopes: string[];

@Column("datetime")
expirationTime: Date;
expirationTime: Date | null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIR we've really never used null as value. Wouldn't setting a date in distant future be less likely to cause problems?

Copy link
Contributor Author

@mustard-mh mustard-mh Jan 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svenefftinge So just add option to allow 5 years? And not show Never expires! but actual expiration date on dashboard?

SCR-20240117-dmpv

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or hard code something like 2099-01-01 00:00:00 as never expires

@mustard-mh
Copy link
Contributor Author

Close as we don't need to modify db #19328 (comment)

@mustard-mh mustard-mh closed this Jan 17, 2024
@mustard-mh mustard-mh deleted the hw/forever-pat branch January 24, 2024 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants