@nebius/js-sdk - v0.2.54
    Preparing search index...

    Interface LifecycleConfiguration

    The lifecycle configuration consists of one or more rules. An Lifecycle configuration can have up to 1,000 rules. Each rule consists of the following:

    • A filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object size, or any combination of these.
    • A status indicating whether the rule is currently active.
    • One or more lifecycle expiration actions that you want to be performed on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended (bucket.spec.versioning_policy equals to ENABLED or SUSPENDED) you can have many versions of the same object (one current version and zero or more noncurrent versions). The system provides predefined actions that you can specify for current and noncurrent object versions.
    interface LifecycleConfiguration {
        "[customJson]"?: () => unknown;
        "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>;
        $type: "nebius.storage.v1.LifecycleConfiguration";
        lastAccessFilter?: LifecycleAccessFilter;
        rules: LifecycleRule[];
        [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined;
    }

    Indexable

    • [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined

      The lifecycle configuration consists of one or more rules. An Lifecycle configuration can have up to 1,000 rules. Each rule consists of the following:

      • A filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object size, or any combination of these.
      • A status indicating whether the rule is currently active.
      • One or more lifecycle expiration actions that you want to be performed on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended (bucket.spec.versioning_policy equals to ENABLED or SUSPENDED) you can have many versions of the same object (one current version and zero or more noncurrent versions). The system provides predefined actions that you can specify for current and noncurrent object versions.
      • Uint8Array<ArrayBufferLike>
      • () => unknown
          • (): unknown

          • The lifecycle configuration consists of one or more rules. An Lifecycle configuration can have up to 1,000 rules. Each rule consists of the following:

            • A filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object size, or any combination of these.
            • A status indicating whether the rule is currently active.
            • One or more lifecycle expiration actions that you want to be performed on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended (bucket.spec.versioning_policy equals to ENABLED or SUSPENDED) you can have many versions of the same object (one current version and zero or more noncurrent versions). The system provides predefined actions that you can specify for current and noncurrent object versions.

            Returns unknown

      • undefined
    Index
    [customJson]? [unknownFieldsSymbol]? $type lastAccessFilter? rules
    "[customJson]"?: () => unknown

    Returns a safe value for JSON logs.

    Type Declaration

      • (): unknown

      • Returns a safe value for JSON logs.

        Returns unknown

    "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>

    Preserves protobuf fields that this SDK version does not recognize.

    $type: "nebius.storage.v1.LifecycleConfiguration"

    Contains the fully qualified protobuf type name.

    lastAccessFilter?: LifecycleAccessFilter

    Specifies which requests are included in days_since_last_access calculations for all transition rules.

    rules: LifecycleRule[]

    Contains the rules protobuf field.

    Settings
    Member Visibility

    On This Page
    Properties