aws-sdk-costexplorer 1.114.0 → 1.115.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f2374b85791a640d979d5b1bd6e063a70f391d93b9ec5b4da8e415ea088ae676
-  data.tar.gz: 565f0866059c9dfe1ee4d193f3fb88985e4ecaa975ef035abe66a86884114548
+  metadata.gz: 0dbea5b3bd8cd3e7760d1887f05abec59afcf5f4b58a555e61e7ddddca22ac60
+  data.tar.gz: dd73334488e38185a68e8e5aae8fc42505ee45e5ca789aefe5274d8cd9574cc5
 SHA512:
-  metadata.gz: acacd9bc83c3a0075a680b75a78c3872ee2b9ec3d7adce0b817f251d14948e3206da62d5aeeebf5f33d93733a01af41a9802c4ae3aa3537c8b1c7ec6f205ba3f
-  data.tar.gz: 453b3a4993497d0bd9f627fcae05f326beabb9f497aff9460eccdc642e633210c0c84b44f114e51e5ddf64e260954d12dbfdaf36352d5aafd871f3c69391e3bf
+  metadata.gz: d6b1981333575697ac13a4a6bf1ac6934df4a7264147f6b374fb555aecae6f8296b39b953fa0883e58fe710895fea1445087aba146c716d95e512c5cc4783cda
+  data.tar.gz: beb804457ed418f0af7e31f8c2e7805a6fc341960223e12637e70ba8215907fb22e001f50c36004a027857901ef46d5d01eca43e51267d75258d15740874cb2b

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.115.0 (2024-11-18)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
 1.114.0 (2024-11-06)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.114.0
+1.115.0

data/lib/aws-sdk-costexplorer/client.rb

@@ -1655,7 +1655,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -1670,7 +1669,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values are
     #         combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is supported.
@@ -1681,7 +1679,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #         [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical operators
@@ -1697,7 +1694,6 @@ module Aws::CostExplorer
     #       "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -2201,7 +2197,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -2216,7 +2211,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values are
     #         combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is supported.
@@ -2227,7 +2221,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #         [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical operators
@@ -2243,7 +2236,6 @@ module Aws::CostExplorer
     #       "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -2711,7 +2703,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -2726,7 +2717,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values are
     #         combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is supported.
@@ -2737,7 +2727,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #         [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical operators
@@ -2753,7 +2742,6 @@ module Aws::CostExplorer
     #       "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -3232,7 +3220,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -3247,7 +3234,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values are
     #         combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is supported.
@@ -3258,7 +3244,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #         [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical operators
@@ -3274,7 +3259,6 @@ module Aws::CostExplorer
     #       "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -4210,7 +4194,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -4225,7 +4208,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values are
     #         combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is supported.
@@ -4236,7 +4218,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #         [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical operators
@@ -4252,7 +4233,6 @@ module Aws::CostExplorer
     #       "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -5356,7 +5336,7 @@ module Aws::CostExplorer
         tracer: tracer
       )
       context[:gem_name] = 'aws-sdk-costexplorer'
-      context[:gem_version] = '1.114.0'
+      context[:gem_version] = '1.115.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-costexplorer/types.rb

@@ -140,7 +140,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -155,7 +154,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -167,7 +165,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -184,7 +181,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -1803,7 +1799,6 @@ module Aws::CostExplorer
     #
     #     * Specify the `Dimensions` field to define a filter that acts on
     #       the [ `DimensionValues` ][1].
-    #
     #   * For each filter type, you can set the dimension name and values
     #     for the filters that you plan to use.
     #
@@ -1818,7 +1813,6 @@ module Aws::CostExplorer
     #
     #     * As shown in the previous example, lists of dimension values are
     #       combined with `OR` when applying the filter.
-    #
     #   * You can also set different match options to further control how
     #     the filter behaves. Not all APIs support match options. Refer to
     #     the documentation for each specific API to see what is supported.
@@ -1829,7 +1823,6 @@ module Aws::CostExplorer
     #     * The corresponding `Expression` for this example is as follows:
     #       `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
     #       [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     # * Compound `Expression` types with logical operations.
     #
     #   * You can use multiple `Expression` types and the logical operators
@@ -1845,7 +1838,6 @@ module Aws::CostExplorer
     #     "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #     "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #     "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #   <note markdown="1"> Because each `Expression` can have only one operator, the service
     #   returns an error if more than one is specified. The following
     #   example shows an `Expression` object that creates an error: ` {
@@ -2481,7 +2473,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -2496,7 +2487,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -2508,7 +2498,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -2525,7 +2514,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -2977,7 +2965,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -2992,7 +2979,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -3004,7 +2990,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -3021,7 +3006,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -3451,7 +3435,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -3466,7 +3449,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -3478,7 +3460,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -3495,7 +3476,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -3778,7 +3758,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -3793,7 +3772,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -3805,7 +3783,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -3822,7 +3799,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {
@@ -4401,7 +4377,6 @@ module Aws::CostExplorer
     #
     #       * Specify the `Dimensions` field to define a filter that acts on
     #         the [ `DimensionValues` ][1].
-    #
     #     * For each filter type, you can set the dimension name and values
     #       for the filters that you plan to use.
     #
@@ -4416,7 +4391,6 @@ module Aws::CostExplorer
     #
     #       * As shown in the previous example, lists of dimension values
     #         are combined with `OR` when applying the filter.
-    #
     #     * You can also set different match options to further control how
     #       the filter behaves. Not all APIs support match options. Refer to
     #       the documentation for each specific API to see what is
@@ -4428,7 +4402,6 @@ module Aws::CostExplorer
     #       * The corresponding `Expression` for this example is as follows:
     #         `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
     #         "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
-    #
     #   * Compound `Expression` types with logical operations.
     #
     #     * You can use multiple `Expression` types and the logical
@@ -4445,7 +4418,6 @@ module Aws::CostExplorer
     #       [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
     #       "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
     #       "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
-    #
     #     <note markdown="1"> Because each `Expression` can have only one operator, the service
     #     returns an error if more than one is specified. The following
     #     example shows an `Expression` object that creates an error: ` {

data/lib/aws-sdk-costexplorer.rb

@@ -54,7 +54,7 @@ module Aws::CostExplorer
   autoload :EndpointProvider, 'aws-sdk-costexplorer/endpoint_provider'
   autoload :Endpoints, 'aws-sdk-costexplorer/endpoints'
 
-  GEM_VERSION = '1.114.0'
+  GEM_VERSION = '1.115.0'
 
 end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-costexplorer
 version: !ruby/object:Gem::Version
-  version: 1.114.0
+  version: 1.115.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-11-06 00:00:00.000000000 Z
+date: 2024-11-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core