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

RS-176: Add license field to ServerInfo #105

Merged
merged 11 commits into from
Feb 28, 2024
Merged

RS-176: Add license field to ServerInfo #105

merged 11 commits into from
Feb 28, 2024

Conversation

atimin
Copy link
Member

@atimin atimin commented Feb 28, 2024

Closes #

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • CHANGELOG.md has been updated (for bug fixes / features / docs)

What kind of change does this PR introduce?

Feature

What was changed?

The SDK has the license field in ServerInfo with the license information:

    info: ServerInfo = await client.info()
    assert info.license.device_number == 1
    assert info.license.device_number == 1
    assert info.license.disk_quota == 0
    assert info.license.expiry_date.isoformat() == "2035-01-01T00:00:00+00:00"
    assert (
        info.license.fingerprint
        == "df92c95a7c9b56c2af99b290c39d8471c3e6cbf9dc33dc9bdb4116b98d465cc9"
    )
    assert info.license.invoice == "xxxxxx"
    assert info.license.licensee == "ReductStore,LLC"
    assert info.license.plan == "UNLIMITED"

Related issues

--

Does this PR introduce a breaking change?

No

Other information:

@atimin atimin changed the title Rs 176 license info RS-176: Add license field to ServerInfo Feb 28, 2024
@atimin atimin merged commit c81992a into main Feb 28, 2024
3 checks passed
@atimin atimin deleted the RS-176-license-info branch February 28, 2024 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant