Introduce Cloud License related GraphQL types
What does this MR do?
Part of https://gitlab.com/gitlab-org/gitlab/-/issues/325541
Introduce GraphQL types and Resolvers for the current license and the license history. The queries are not used yet but will be needed for frontend related work that is being done in https://gitlab.com/gitlab-org/gitlab/-/issues/273028.
Local testing
- Navigate to
http://localhost:3000/-/graphql-explorer
- Query the current license with the following:
query {
currentLicense {
id
type
plan
name
email
company
startsAt
expiresAt
activatedAt
lastSync
usersInLicenseCount
billableUsersCount
maximumUserCount
usersOverLicenseCount
}
}
- and query the license history with:
query {
licenseHistoryEntries {
nodes {
id
type
plan
name
email
company
usersInLicenseCount
startsAt
expiresAt
activatedAt
}
}
}
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because it is a developer facing change and the code will be used in the frontend companion issue.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Corinna Gogolok