Optionaldata: PartialMessage<RegistryItemBilling>The recurring monthly cost of the item, broken down by billable resource.
The recurring yearly cost of the item, broken down by billable resource.
Static ReadonlyfieldsStatic ReadonlyruntimeStatic ReadonlytypeCreate a deep copy.
Compare with a message of the same type. Note that this function disregards extensions and unknown fields.
Parse from binary data, merging fields.
Repeated fields are appended. Map entries are added, overwriting existing keys.
If a message field is already present, it will be merged with the new data.
Optionaloptions: Partial<BinaryReadOptions>Parse a message from a JSON value.
Optionaloptions: Partial<JsonReadOptions>Parse a message from a JSON string.
Optionaloptions: Partial<JsonReadOptions>Retrieve the MessageType of this message - a singleton that represents the protobuf message declaration and provides metadata for reflection- based operations.
Serialize the message to binary data.
Optionaloptions: Partial<BinaryWriteOptions>Serialize the message to a JSON value, a JavaScript value that can be passed to JSON.stringify().
Optionaloptions: Partial<JsonWriteOptions>ProtectedtoOverride for serialization behavior. This will be invoked when calling JSON.stringify on this message (i.e. JSON.stringify(msg)).
Note that this will not serialize google.protobuf.Any with a packed message because the protobuf JSON format specifies that it needs to be unpacked, and this is only possible with a type registry to look up the message type. As a result, attempting to serialize a message with this type will throw an Error.
This method is protected because you should not need to invoke it directly -- instead use JSON.stringify or toJsonString for stringified JSON. Alternatively, if actual JSON is desired, you should use toJson.
Serialize the message to a JSON string.
Optionaloptions: Partial<JsonWriteStringOptions>StaticequalsStaticfromOptionaloptions: Partial<BinaryReadOptions>StaticfromOptionaloptions: Partial<JsonReadOptions>StaticfromOptionaloptions: Partial<JsonReadOptions>
RegistryItemBilling stores usage cost information for a registry item. Its shape mirrors the billing block used by fragments so that billing jobs can consume registry item costs the same way. For now only cost_per_month.per_machine is supported; the additional fields that fragment billing supports (cost_per_year, tier_name, in_arrears, etc.) are intentionally omitted.
Generated
from message viam.app.v1.RegistryItemBilling