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.

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

Remove grace period from license expiration check #67316

Merged
merged 1 commit into from
Feb 12, 2021

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Jan 12, 2021

License expiration checking currently has a 7 day grace period. When a
license expires, the licensing code acts as if it is not yet expired.
This was originally intended to protect users who may accidentally end up
letting their license expire from the pain of their licensed features
ceasing to work. However, the grace period effectively shifts the
license expiration by a week, resulting in confusion since the actual
license expiration date is not accurate. It also is less of a concern
now as not only do we emit several warnings for upcoming license
expiration, but the new license can be downloaded and installed quickly
by the user through the support portal.

This commit removes the license grace period altogether.

License expiration checking currently has a 7 day grace period. When a
license expires, the licensing code acts as if it is not yet expired.
This was originally intended to protect users who may accidentally end up
letting their license expire from the pain of their licensed features
ceasing to work. However, the grace period effectively shifts the
license expiration by a week, resulting in confusion since the actual
license expiration date is not accurate. It also is less of a concern
now as not only do we emit several warnings for upcoming license
expiration, but the new license can be downloaded and installed quickly
by the user through the support portal.

This commit removes the license grace period altogether.
@rjernst rjernst added >breaking :Security/License License functionality for commercial features v8.0.0 v7.12.0 labels Jan 12, 2021
@elasticmachine elasticmachine added the Team:Security Meta label for security team label Jan 12, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@rjernst
Copy link
Member Author

rjernst commented Jan 12, 2021

Note that I have marked this as >breaking even though it is not actually breaking, since it is not related to any API a user uses. Unfortunately I don't see an existing category label that can describe such a behavior change which doesn't actually affect users, but is still included in the release notes.

@rjernst rjernst requested a review from jasontedor January 12, 2021 03:57
@bytebilly
Copy link
Contributor

Thanks @rjernst, I agree it is not a breaking change for users as the grace period is not something they know/rely on.

@mark-vieira
Copy link
Contributor

@elasticmachine update branch

Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

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

LGTM.

@rjernst rjernst merged commit c0b7f76 into elastic:master Feb 12, 2021
@rjernst rjernst deleted the refactor_license17 branch February 12, 2021 00:22
rjernst added a commit that referenced this pull request Feb 12, 2021
License expiration checking currently has a 7 day grace period. When a
license expires, the licensing code acts as if it is not yet expired.
This was originally intended to protect users who may accidentally end up
letting their license expire from the pain of their licensed features
ceasing to work. However, the grace period effectively shifts the
license expiration by a week, resulting in confusion since the actual
license expiration date is not accurate. It also is less of a concern
now as not only do we emit several warnings for upcoming license
expiration, but the new license can be downloaded and installed quickly
by the user through the support portal.

This commit removes the license grace period altogether.
@williamrandolph
Copy link
Contributor

I will put this under "Enhancements" in the release notes so that it's not the first thing that users see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>breaking :Security/License License functionality for commercial features Team:Security Meta label for security team v7.12.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants