-
Notifications
You must be signed in to change notification settings - Fork 350
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
License nagging #1455
License nagging #1455
Conversation
The latest Buf updates on your PR. Results from workflow Buf CI / push-module (pull_request).
|
enterpriseFeatures, err := s.adminapiCl.GetEnterpriseFeatures(ctx) | ||
if err == nil { | ||
isViolation = enterpriseFeatures.Violation | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if GetEnterpriseFeatures
fails we default to "no violation"... is that intentional?
Couldn't just someone turn off / ensure this endpoint fails and always have a valid license?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes this is intentional, since we will also be dealing with Redpanda clusters that do not yet implement this new endpoint. It is not a problem, because this is just some soft nagging / reminding the users that they are violating the license. If we are not certain they are violating the license we better be quiet was the idea here
frontend/src/state/backendApi.ts
Outdated
this.enterpriseFeaturesUsed = enterpriseFeaturesResponse.features; | ||
|
||
// Handle the second response | ||
this.licenses = licensesResponse.licenses; | ||
this.licenseViolation = licensesResponse.violation; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what if enterpriseFeaturesResponse
is of type Errorr? which can happen because ofthe catch and "return err" in line 1567
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rikimaru0345 can you please check now?
@jvorcak Also, I am confused why we still see different license status in license details. Uploading an Enterprise license is supposed to also push the license to the Redpanda cluster (what now says 'Core Community'). This part should should say 'Repanda Community Edition' or 'Redpanda Enterprise Edition', and after upload of a license at a minimum both should be 'Enterprise'. The Console one should be 'Console Community Edition', 'Console Enterprise Edition. Also, a header for 'Expiry Date' column would be nice. |
@mattschumpert I've addressed the details we talked about in #1464 |
This pull request changes:
ListEnterpriseFeatures
RPC to console pkg (may return CodeUnimplemented if unreachable or unimplemented)violation
bool in ListLicenses response (defaults to false if admin api endpoint is unreachable or unimplemented)Has a dependency on: redpanda-data/common-go#24