datadog-agent
datadog-agent copied to clipboard
Bump github.com/aws/aws-sdk-go-v2/service/ecs from 1.35.1 to 1.38.1 in /test/new-e2e
Bumps github.com/aws/aws-sdk-go-v2/service/ecs from 1.35.1 to 1.38.1.
Changelog
Sourced from github.com/aws/aws-sdk-go-v2/service/ecs's changelog.
Release (2023-08-01)
General Highlights
- Dependency Update: Updated to the latest SDK module versions
Module Highlights
github.com/aws/aws-sdk-go-v2/service/batch: v1.26.0
- Feature: This release adds support for price capacity optimized allocation strategy for Spot Instances.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.29.0
- Feature: Adding new API describe-engine-versions which provides information about the lifecycle of a replication instance's version.
github.com/aws/aws-sdk-go-v2/service/internetmonitor: v1.5.0
- Feature: This release adds a new feature for Amazon CloudWatch Internet Monitor that enables customers to set custom thresholds, for performance and availability drops, for impact limited to a single city-network to trigger creation of a health event.
github.com/aws/aws-sdk-go-v2/service/medialive: v1.34.0
- Feature: AWS Elemental Link devices now report their Availability Zone. Link devices now support the ability to change their Availability Zone.
github.com/aws/aws-sdk-go-v2/service/polly: v1.29.0
- Feature: Amazon Polly adds new French Belgian voice - Isabelle. Isabelle is available as Neural voice only.
github.com/aws/aws-sdk-go-v2/service/rds: v1.50.0
- Feature: Added support for deleted clusters PiTR.
github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.97.0
- Feature: Add Stairs TrafficPattern and FlatInvocations to RecommendationJobStoppingConditions
Release (2023-07-31)
General Highlights
- Feature: Adds support for smithy-modeled endpoint resolution. A new rules-based endpoint resolution will be added to the SDK which will supercede and deprecate existing endpoint resolution. Specifically, EndpointResolver will be deprecated while BaseEndpoint and EndpointResolverV2 will take its place. For more information, please see the Endpoints section in our Developer Guide.
- Dependency Update: Updated to the latest SDK module versions
Module Highlights
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.12.0
- Feature: Amplify Studio releases GraphQL support for codegen job action.
github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.30.0
- Feature: You can now configure an instance refresh to set its status to 'failed' when it detects that a specified CloudWatch alarm has gone into the ALARM state. You can also choose to roll back the instance refresh automatically when the alarm threshold is met.
github.com/aws/aws-sdk-go-v2/service/cleanrooms: v1.3.0
- Feature: This release introduces custom SQL queries - an expanded set of SQL you can run. This release adds analysis templates, a new resource for storing pre-defined custom SQL queries ahead of time. This release also adds the Custom analysis rule, which lets you approve analysis templates for querying.
github.com/aws/aws-sdk-go-v2/service/codestarconnections: v1.15.0
- Feature: New integration with the Gitlab provider type.
github.com/aws/aws-sdk-go-v2/service/drs: v1.15.0
- Feature: Add support for in-aws right sizing
github.com/aws/aws-sdk-go-v2/service/inspector2: v1.16.0
- Feature: This release adds 1 new API: BatchGetFindingDetails to retrieve enhanced vulnerability intelligence details for findings.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.18.0
- Feature: This release includes new import resource, model versioning and resource policy features.
github.com/aws/aws-sdk-go-v2/service/omics: v1.6.0
- Feature: Add CreationType filter for ListReadSets
github.com/aws/aws-sdk-go-v2/service/rds: v1.49.0
- Feature: This release adds support for Aurora MySQL local write forwarding, which allows for forwarding of write operations from reader DB instances to the writer DB instance.
github.com/aws/aws-sdk-go-v2/service/route53: v1.29.0
- Feature: Amazon Route 53 now supports the Israel (Tel Aviv) Region (il-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region.
github.com/aws/aws-sdk-go-v2/service/scheduler: v1.2.0
- Feature: This release introduces automatic deletion of schedules in EventBridge Scheduler. If configured, EventBridge Scheduler automatically deletes a schedule after the schedule has completed its last invocation.
... (truncated)
Commits
1f2e30dRelease 2023-08-01df6e948Regenerated Clientsfdabee0Update partitions file95f0a25Update endpoints model2b58c3cUpdate API model787a818Release 2023-07-31953c852Regenerated Clients9ad4f50Update SDK's smithy-go dependency to v1.14.0bd77e8dUpdate partitions file7a0433fUpdate endpoints model- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: cbc920eb-0620-4e07-aa42-a88e946c0de8 Baseline: 5d2a79a61d2da5a71197cdf9e696b9b42117e874 Comparison: c73bf380e88eca586511d893f014b50ed5eba3ad Total CPUs: 7
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
Experiments with missing or malformed data
- basic_py_check
Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.
No significant changes in experiment optimization goals
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Experiments ignored for regressions
Regressions in experiments with settings containing erratic: true are ignored.
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +1.64 | [-5.00, +8.27] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +1.64 | [-5.00, +8.27] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +1.28 | [+1.23, +1.33] |
| ➖ | idle | memory utilization | +0.36 | [+0.33, +0.39] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.34 | [+0.31, +0.38] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.25 | [+0.21, +0.28] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | trace_agent_json | ingress throughput | -0.01 | [-0.05, +0.02] |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.02 | [-1.46, +1.41] |
| ➖ | trace_agent_msgpack | ingress throughput | -0.02 | [-0.03, -0.02] |
| ➖ | otel_to_otel_logs | ingress throughput | -0.05 | [-0.66, +0.55] |
| ➖ | process_agent_standard_check | memory utilization | -0.07 | [-0.11, -0.02] |
| ➖ | file_tree | memory utilization | -0.23 | [-0.30, -0.15] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
@dependabot rebase