Change: deprecate environment storage bytesUsed for kibUsed #3658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General Checklist
Database Migrations
This introduces a deprecation on
bytesUsed
when interacting with environment storage queries and mutations.When retrieving environment storage sizes,
bytesUsed
is provided as the name when the value of this data is actually kibibytes. This PR is the first step in the removal ofbytesUsed
and renaming tokibUsed
. A follow up PR will introduce the actual breaking change to remove it in a future release.Additionally,
bytesUsed
is anInt
type, which has a 32bit integer limitation. The newkibUsed
input is aFloat
type to allow greater input.For now,
bytesUsed
is still the required input foraddOrUpdateEnvironmentStorage
withkibUsed
as an optional argument.kibUsed
will be preferred though if it is provided. Unfortunately, asbytesUsed
is still anInt
large numbers will still cause an error if they are provided, untilbytesUsed
is completely removed from the API in a future versionClosing issues
closes #2245