Aperture-py

Latest version: v2.26.0

Safety actively analyzes 688674 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 29 of 53

2.1.0rc.2

Changelog

List of aperture PRs merged since 2.0.0 release. For the full list of changes, see [list of changes][changes]

Bump OTEL to v0.77.0 (1929)

Description of change
* Update OTel to `v0.77.0`. This enforces Prometheus metric names
normalizer, so some metric names are updates:
* `regulator_counter`->`regulator_counter_total`
* `classifier_counter`->`classifier_counter_total`
* `rate_limiter_counter`->`rate_limiter_counter_total`
* `k8s_pod_cpu_utilization`->`k8s_pod_cpu_utilization_ratio`
* `k8s_pod_memory_usage`->`k8s_pod_memory_usage_bytes`
* Drive-by: clean up of metric names consts

**Refactor:**
- Removed unused dotnetdiagnosticsreceiver Go module
- Updated language_version for black hook in .pre-commit-config.yaml
- Improved metric names, Prometheus queries, error messages, and
replaced hard-coded strings with constants

> 🎉 Oh rejoice, the code is clean,
> Unused modules no longer seen.
> Constants rise, strings take flight,
> Our codebase shines, a beacon of light! 🌟

---------

Co-authored-by: Krzysztof Kwapisiewicz <krzysztof.kwapisiewiczfluxninja.com>

scheduler: pass through when not in overload (1944)


Implement Alerters defined inside AutoScaler (1941)


Add scale in controller that periodically scales down (1923)

Description of change

![Screenshot from 2023-05-11
10-39-20](https://github.com/fluxninja/aperture/assets/1553055/7279692b-bce0-41e6-8b99-d8b244f39516)

![Screenshot from 2023-05-11
10-39-29](https://github.com/fluxninja/aperture/assets/1553055/64fcf92b-595b-4210-9c26-4aafc5b2566c)

**New Feature:**
- Added `PeriodicDecrease` controller for auto-scaling based on a
periodic timer
- Modified `ScaleInController` message to include the new
`PeriodicDecrease` controller

> 🎉 A timer ticks, replicas shrink,
> With PeriodicDecrease, we sync.
> Scaling down, a rhythm found,
> In this PR, new features abound! 🚀

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>

Stop crashing agent on implicit infra meter pipeline (1928)

Fixes 1925

Update modules to aperture v2 (1919)

Golang modules' paths changed to aperture/v2.

Move output ports inside scaling backend (1922)

**Refactor:**
- Moved output ports for KubernetesReplicas inside ScalingBackend
message
- Replaced OutPorts message in AutoScaler with new Outs message in
KubernetesReplicas
- Adjusted dry_run parameter position

> 🎉 A refactor we did embrace, 🔄
> In ScalingBackend, found its place. 🌐
> Output ports now rearranged, 🚪
> With code logic re-engaged! 💻

do not panic on shutdown errors (1905)


Bug fix:
- Changed log level from `Panic` to `Error` in the `Shutdown` function of pkg/utils/helpers.go


> 🎉 Hooray for this change, so small and neat,
> No more panic, just errors we'll meet.
> A smoother shutdown, that's what we cheer,
> With every release, progress is near! 🚀

shutdown process when otel config is incorrect (1904)

Description of change

Shutdown process when OTel configuration has issues.

**Bug fix:**
- Improved shutdown handling in various parts of the codebase
- Updated `Shutdown` function to use `log.Panic` instead of `log.Error`

**Refactor:**
- Replaced direct calls to `Shutdowner.Shutdown` with utility function
`utils.Shutdown`

> 🎉 A graceful exit we now embrace,
> With Shutdown's touch, a safer space.
> Refactored code, a cleaner slate,
> In this PR, we celebrate! 🥳

telemetry resource: update etcd path to use policy name (1901)

Description of change

Prevent clash in telemetry collector etcd paths across policies

**Bug fix:**
- Prevent clashes in telemetry collector etcd paths across policies by
updating the path and key functions
- Update `NewClassifierOptions` function call to use an integer index
instead of int64

> 🎉 No more clashes, our paths are clear,
> With updated keys, we have nothing to fear.
> A small change in type, but a big win,
> Our code is now stronger, let the celebration begin! 🥳

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v2.0.0...releases/aperture-controller/v2.1.0-rc.2

2.1.0rc.1

Changelog

List of aperture PRs merged since 2.0.0 release. For the full list of changes, see [list of changes][changes]

Add scale in controller that periodically scales down (1923)

Description of change

![Screenshot from 2023-05-11
10-39-20](https://github.com/fluxninja/aperture/assets/1553055/7279692b-bce0-41e6-8b99-d8b244f39516)

![Screenshot from 2023-05-11
10-39-29](https://github.com/fluxninja/aperture/assets/1553055/64fcf92b-595b-4210-9c26-4aafc5b2566c)


Checklist

- [x] Tested in playground or other setup
- [x] Screenshot (Grafana) from playground added to PR for 15+ minute
run
- [x] Documentation is changed or added
- [ ] Tests and/or benchmarks are included
- [ ] Breaking changes

<!-- This is an auto-generated comment: release notes by openai -->
Summary by OpenAI

**New Feature:**
- Added `PeriodicDecrease` controller for auto-scaling based on a
periodic timer
- Modified `ScaleInController` message to include the new
`PeriodicDecrease` controller

> 🎉 A timer ticks, replicas shrink,
> With PeriodicDecrease, we sync.
> Scaling down, a rhythm found,
> In this PR, new features abound! 🚀
<!-- end of auto-generated comment: release notes by openai -->

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>

Stop crashing agent on implicit infra meter pipeline (1928)

Fixes 1925

Update modules to aperture v2 (1919)

Golang modules' paths changed to aperture/v2.

Move output ports inside scaling backend (1922)

Summary by OpenAI

**Refactor:**
- Moved output ports for KubernetesReplicas inside ScalingBackend
message
- Replaced OutPorts message in AutoScaler with new Outs message in
KubernetesReplicas
- Adjusted dry_run parameter position

> 🎉 A refactor we did embrace, 🔄
> In ScalingBackend, found its place. 🌐
> Output ports now rearranged, 🚪
> With code logic re-engaged! 💻
<!-- end of auto-generated comment: release notes by openai -->

do not panic on shutdown errors (1905)

<!-- This is an auto-generated comment: release notes by openai -->
Summary by OpenAI


Bug fix:
- Changed log level from `Panic` to `Error` in the `Shutdown` function of pkg/utils/helpers.go


> 🎉 Hooray for this change, so small and neat,
> No more panic, just errors we'll meet.
> A smoother shutdown, that's what we cheer,
> With every release, progress is near! 🚀
<!-- end of auto-generated comment: release notes by openai -->

shutdown process when otel config is incorrect (1904)

Description of change

Shutdown process when OTel configuration has issues.

<!-- This is an auto-generated comment: release notes by openai -->
Summary by OpenAI

**Bug fix:**
- Improved shutdown handling in various parts of the codebase
- Updated `Shutdown` function to use `log.Panic` instead of `log.Error`

**Refactor:**
- Replaced direct calls to `Shutdowner.Shutdown` with utility function
`utils.Shutdown`

> 🎉 A graceful exit we now embrace,
> With Shutdown's touch, a safer space.
> Refactored code, a cleaner slate,
> In this PR, we celebrate! 🥳
<!-- end of auto-generated comment: release notes by openai -->

always build aperturectl (1903)

openai: ignore

chore: refactor fx tags (1902)

Description of change

openai: ignore

telemetry resource: update etcd path to use policy name (1901)

Description of change

Prevent clash in telemetry collector etcd paths across policies

<!-- This is an auto-generated comment: release notes by openai -->
Summary by OpenAI

**Bug fix:**
- Prevent clashes in telemetry collector etcd paths across policies by
updating the path and key functions
- Update `NewClassifierOptions` function call to use an integer index
instead of int64

> 🎉 No more clashes, our paths are clear,
> With updated keys, we have nothing to fear.
> A small change in type, but a big win,
> Our code is now stronger, let the celebration begin! 🥳
<!-- end of auto-generated comment: release notes by openai -->

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v2.0.0...releases/aperture-controller/v2.1.0-rc.1

2.0.0

Changelog

List of aperture PRs merged since 1.6.0 release. For the full list of changes, see [list of changes][changes]

Updated metrics documentation (1896)

- Added a script to generate md files for all the integrations listed in
the metadata file

**New Feature:**
- Added OpenTelemetry Collector integrations for `write_http` and
`Kubelet`
- Introduced a script to generate documentation for OpenTelemetry
Collector integrations

**Documentation:**
- Updated Policy resources documentation with new OpenTelemetry
Collector integrations
- Improved example YAML configurations and instructions for configuring
OpenTelemetry Collector integrations

> 🎉 A new dawn for metrics, we pave the way,
> With OpenTelemetry integrations on display.
> Docs generated with ease, a script so fine,
> Our users rejoice, as their metrics align. 📊

Infra Meters (1890)


Refactor policy specs (1893)

Description of change
* Remove redundant _parameter suffix in policy fields.
* Refactor autoscale proto to allow re-use of its schemas within
autoscale blueprints.
* Documentation improvements

**New Feature**:
- Added `ScalingBackend` message with `KubernetesReplicas` scaler
- Introduced `dry_run` and `dry_run_config_key` fields

**Refactor**:
- Reused autoscale proto schemas within autoscale blueprints
- Removed redundant _parameter suffix in policy fields
- Renamed various fields and parameters
- Updated structure of various fields

**Documentation**:
- Improved documentation across multiple files
- Changed terminology for a key feature

> 🎉 Hooray for the changes we've made,
> Scaling backends, new fields displayed! 🚀
> Refactored code, docs improved too,
> A celebration is surely due! 🥳

remove latency_baseliner from promql SP blueprint (1891)


refactor various precommit and install tools steps (1884)

**Chore:**
- Updated CircleCI executor image, cache keys, and pre-commit hooks.
- Added separate scripts for installing asdf, Go, Node.js, and Python
tools.
- Replaced `npx` commands with direct calls to the respective tools.
- Removed redundant calls and improved installation processes.

> 🎉 A PR of change, a dance of code,
> Tools updated, a lighter load.
> Scripts refined, installations smart,
> Embrace the future, a fresh new start. 🚀

make parameters and alerter required fields in AdaptiveLoadScheduler (1882)

Description of change

Make the fields required instead of relying on nil pointer checks and
setting default behavior manually.

**New Feature:**
- Make `gradient`, `alerter`, `Parameters`, and `Alerter` fields
required in `AdaptiveLoadScheduler`
- Set default value for `AlertName` if not provided

> 🎉 With fields required, we stand tall,
> No more nil checks, we've fixed them all.
> A default alert name, now in place,
> Our scheduler's stronger, keeping pace. 🚀

Playground: Prometheus scenario with workload prioritization policy (1872)

**New Feature:**
- Added remote writes endpoint to demoapp for Prometheus integration
- Introduced service protection policy with classifier based on metrics
name
- Support for custom values per scenario for aperture and demo-app
components
- Fixed missing agent config for RabbitMQ queue buildup scenario

**Documentation:**
- Updated documentation for workload prioritization policy and custom
values

> 🎉 A new horizon, we now see,
> With metrics and protection, in harmony. 🛡️
> Custom values, scenarios unfold,
> As RabbitMQ's secrets are told. 🐇

Refactor LoadScheduler (1876)

Description of change

Refactored LoadScheduler

**New Feature**:
- Added new messages and modified existing ones in protobuf files
- Removed private properties from the `properties` map of a definition
- Refactored LoadScheduler and updated related blueprints
- Introduced overload confirmation criteria schema

**Documentation**:
- Updated documentation for renamed components and added new blueprint
page

> 🎉 A PR so grand, with changes at hand,
> Protobufs refined, and logic combined,
> LoadScheduler's new face, overload criteria in place,
> Docs up to date, let's celebrate! 🥳

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>
Co-authored-by: Hasit Mistry <hasitfluxninja.com>

Weighted scenario (1874)

Description of change
Update source, destination services label
- Rename source_service, destination_service -> source_fqdns,
destination_fqdns
- Add new scenario

k6 -> svc1 -> svc3, k6 -> svc2 -> svc3
- add new policy to give higher priority to guest flow from svc1 than
guest flow from svc2
- Fix label_matcher

Make label_exists not required
- Update example

![Screenshot from 2023-05-03
19-11-51](https://user-images.githubusercontent.com/1553055/236096226-e3d38684-c529-4709-a107-140743ced2f7.png)

**New Feature:**
- Added a new scenario to prioritize guest flow from svc1 over svc2
- Updated label matching and removed `label_exists` requirement

**Refactor:**
- Renamed `source_service` and `destination_service` to `source_fqdns`
and `destination_fqdns`

**Test:**
- Updated k6 script with a new scenario and label matcher changes

> 🎉 A new scenario takes the stage,
> Prioritizing flows, an update we gauge.
> Labels match with ease, no need to exist,
> Renamed variables, a twist in the midst. 🔄

Refactor overload confirmation (1867)

Description of change
* Rename port and signals: enabled -> overload_confirmation.
* Behavior: Additional criteria for determining overload in
`AdaptiveLoadScheduler` instead of an enable/disable switch for load
throttling.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v1.6.0...releases/aperture-controller/v2.0.0

2.0.0rc.2

Changelog

List of aperture PRs merged since 1.6.0 release. For the full list of changes, see [list of changes][changes]

Updated metrics documentation (1896)

- Added a script to generate md files for all the integrations listed in
the metadata file

**New Feature:**
- Added OpenTelemetry Collector integrations for `write_http` and
`Kubelet`
- Introduced a script to generate documentation for OpenTelemetry
Collector integrations

**Documentation:**
- Updated Policy resources documentation with new OpenTelemetry
Collector integrations
- Improved example YAML configurations and instructions for configuring
OpenTelemetry Collector integrations

> 🎉 A new dawn for metrics, we pave the way,
> With OpenTelemetry integrations on display.
> Docs generated with ease, a script so fine,
> Our users rejoice, as their metrics align. 📊

Infra Meters (1890)


Refactor policy specs (1893)

Description of change
* Remove redundant _parameter suffix in policy fields.
* Refactor autoscale proto to allow re-use of its schemas within
autoscale blueprints.
* Documentation improvements

**New Feature**:
- Added `ScalingBackend` message with `KubernetesReplicas` scaler
- Introduced `dry_run` and `dry_run_config_key` fields

**Refactor**:
- Reused autoscale proto schemas within autoscale blueprints
- Removed redundant _parameter suffix in policy fields
- Renamed various fields and parameters
- Updated structure of various fields

**Documentation**:
- Improved documentation across multiple files
- Changed terminology for a key feature

> 🎉 Hooray for the changes we've made,
> Scaling backends, new fields displayed! 🚀
> Refactored code, docs improved too,
> A celebration is surely due! 🥳

remove latency_baseliner from promql SP blueprint (1891)


refactor various precommit and install tools steps (1884)

**Chore:**
- Updated CircleCI executor image, cache keys, and pre-commit hooks.
- Added separate scripts for installing asdf, Go, Node.js, and Python
tools.
- Replaced `npx` commands with direct calls to the respective tools.
- Removed redundant calls and improved installation processes.

> 🎉 A PR of change, a dance of code,
> Tools updated, a lighter load.
> Scripts refined, installations smart,
> Embrace the future, a fresh new start. 🚀

make parameters and alerter required fields in AdaptiveLoadScheduler (1882)

Description of change

Make the fields required instead of relying on nil pointer checks and
setting default behavior manually.

**New Feature:**
- Make `gradient`, `alerter`, `Parameters`, and `Alerter` fields
required in `AdaptiveLoadScheduler`
- Set default value for `AlertName` if not provided

> 🎉 With fields required, we stand tall,
> No more nil checks, we've fixed them all.
> A default alert name, now in place,
> Our scheduler's stronger, keeping pace. 🚀

Playground: Prometheus scenario with workload prioritization policy (1872)

**New Feature:**
- Added remote writes endpoint to demoapp for Prometheus integration
- Introduced service protection policy with classifier based on metrics
name
- Support for custom values per scenario for aperture and demo-app
components
- Fixed missing agent config for RabbitMQ queue buildup scenario

**Documentation:**
- Updated documentation for workload prioritization policy and custom
values

> 🎉 A new horizon, we now see,
> With metrics and protection, in harmony. 🛡️
> Custom values, scenarios unfold,
> As RabbitMQ's secrets are told. 🐇

Refactor LoadScheduler (1876)

Description of change

Refactored LoadScheduler

**New Feature**:
- Added new messages and modified existing ones in protobuf files
- Removed private properties from the `properties` map of a definition
- Refactored LoadScheduler and updated related blueprints
- Introduced overload confirmation criteria schema

**Documentation**:
- Updated documentation for renamed components and added new blueprint
page

> 🎉 A PR so grand, with changes at hand,
> Protobufs refined, and logic combined,
> LoadScheduler's new face, overload criteria in place,
> Docs up to date, let's celebrate! 🥳

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>
Co-authored-by: Hasit Mistry <hasitfluxninja.com>

Weighted scenario (1874)

Description of change
Update source, destination services label
- Rename source_service, destination_service -> source_fqdns,
destination_fqdns
- Add new scenario

k6 -> svc1 -> svc3, k6 -> svc2 -> svc3
- add new policy to give higher priority to guest flow from svc1 than
guest flow from svc2
- Fix label_matcher

Make label_exists not required
- Update example

![Screenshot from 2023-05-03
19-11-51](https://user-images.githubusercontent.com/1553055/236096226-e3d38684-c529-4709-a107-140743ced2f7.png)

**New Feature:**
- Added a new scenario to prioritize guest flow from svc1 over svc2
- Updated label matching and removed `label_exists` requirement

**Refactor:**
- Renamed `source_service` and `destination_service` to `source_fqdns`
and `destination_fqdns`

**Test:**
- Updated k6 script with a new scenario and label matcher changes

> 🎉 A new scenario takes the stage,
> Prioritizing flows, an update we gauge.
> Labels match with ease, no need to exist,
> Renamed variables, a twist in the midst. 🔄

Refactor overload confirmation (1867)

Description of change
* Rename port and signals: enabled -> overload_confirmation.
* Behavior: Additional criteria for determining overload in
`AdaptiveLoadScheduler` instead of an enable/disable switch for load
throttling.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v1.6.0...releases/aperture-controller/v2.0.0-rc.2

2.0.0rc.1

Changelog

List of aperture PRs merged since 1.6.0 release. For the full list of changes, see [list of changes][changes]

Playground: Prometheus scenario with workload prioritization policy (1872)

**New Feature:**
- Added remote writes endpoint to demoapp for Prometheus integration
- Introduced service protection policy with classifier based on metrics
name
- Support for custom values per scenario for aperture and demo-app
components
- Fixed missing agent config for RabbitMQ queue buildup scenario

**Documentation:**
- Updated documentation for workload prioritization policy and custom
values

> 🎉 A new horizon, we now see,
> With metrics and protection, in harmony. 🛡️
> Custom values, scenarios unfold,
> As RabbitMQ's secrets are told. 🐇

Refactor LoadScheduler (1876)

**New Feature**:
- Added new messages and modified existing ones in protobuf files
- Removed private properties from the `properties` map of a definition
- Refactored LoadScheduler and updated related blueprints
- Introduced overload confirmation criteria schema

**Documentation**:
- Updated documentation for renamed components and added new blueprint
page

> 🎉 A PR so grand, with changes at hand,
> Protobufs refined, and logic combined,
> LoadScheduler's new face, overload criteria in place,
> Docs up to date, let's celebrate! 🥳

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>
Co-authored-by: Hasit Mistry <hasitfluxninja.com>

Weighted scenario (1874)

Description of change
Update source, destination services label
- Rename source_service, destination_service -> source_fqdns,
destination_fqdns
- Add new scenario

k6 -> svc1 -> svc3, k6 -> svc2 -> svc3
- add new policy to give higher priority to guest flow from svc1 than
guest flow from svc2
- Fix label_matcher

Make label_exists not required
- Update example

![Screenshot from 2023-05-03
19-11-51](https://user-images.githubusercontent.com/1553055/236096226-e3d38684-c529-4709-a107-140743ced2f7.png)

**New Feature:**
- Added a new scenario to prioritize guest flow from svc1 over svc2
- Updated label matching and removed `label_exists` requirement

**Refactor:**
- Renamed `source_service` and `destination_service` to `source_fqdns`
and `destination_fqdns`

**Test:**
- Updated k6 script with a new scenario and label matcher changes

> 🎉 A new scenario takes the stage,
> Prioritizing flows, an update we gauge.
> Labels match with ease, no need to exist,
> Renamed variables, a twist in the midst. 🔄

Refactor overload confirmation (1867)

Description of change
* Rename port and signals: enabled -> overload_confirmation.
* Behavior: Additional criteria for determining overload in
`AdaptiveLoadScheduler` instead of an enable/disable switch for load
throttling.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v1.6.0...releases/aperture-controller/v2.0.0-rc.1

1.6.0

Changelog

List of aperture PRs merged since 1.5.0 release. For the full list of changes, see [list of changes][changes]

fix remark validate link issues (1853)


Multi selectors (1826)

Description of change

Support for repeated selector field in all data-plane components.

![Screenshot from 2023-04-30
21-35-47](https://user-images.githubusercontent.com/18579817/235407302-efe30bed-bdcf-407c-9246-51ebdf9d9650.png)

**New Feature:**
- Support for repeated selector fields in all data-plane components
- Added `MatchWithResultCollection` method to the `MultiMatcher` struct
- New `GetSelectors()` method and related changes in various interfaces
and structs

**Documentation:**
- Updated documentation files with minor changes, including fixing
broken links, typos, and modifying titles and descriptions

> 🎉 Repeated selectors, now we're able,
> To scale our components, oh so stable!
> Docs refined, code's aligned,
> With this PR, we've truly shined! 🌟

---------

Co-authored-by: Tanveer Gill <tanveer.gillfluxninja.com>

Use connector to direct traces to logs (1807)

Implement adapter connector which converts traces to logs. Use this
adapter in pipeline instead of loopback hack.

**New Feature:**
- Added adapter connector to convert traces to logs, replacing loopback
hack
- Removed `tracestologsprocessor` factory and introduced
`adapterconnector` factory
- Removed `filelog` receiver and fake log pipeline
- Updated `OTelConfig` struct with new fields and methods

> 🎉 A new dawn for trace conversion,
> Adapter connector brings a revolution.
> Farewell to the loopback hack,
> With this update, we're on the right track! 🚀

Made the gateway address change backward compatible (1821)

**New Feature:**
- Added backward compatibility checks for older default addresses
- Updated field mappings for component conversion

> 🎉 A step back in time we take, 🕰️
> To ensure compatibility we make. 🛠️
> Field mappings now renewed, 🔄
> For a future that's well-reviewed. 🌟

Backward compatibility helper and other improvements (1818)

Description of change
* Helper function to rewrite specs for backward compatibility reduced
code repetition).
* Minor suggestions by OpenAI.
* Incorporates improvements suggested in
https://github.com/fluxninja/aperture/pull/1792


- New Feature: Improved flow control components and circuit factory logic
- Bug fix: Addressed issues in table structure and column names
- Documentation: Updated comments and documentation for better clarity
- Refactor: Modified helper functions, test cases, and function names for consistency

> 🎉 Flow control's now refined,
> With bugs and issues left behind.
> Docs are clear, code's robust,
> In this PR we place our trust. 🚀


---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

Renaming components for clarity (1792)

Description of change
* Renames:
* ConcurrencyLimiter -> LoadScheduler
* AIMDConcurrencyLimiter -> AdaptiveLoadScheduler
* LoadRegulator -> Regulator
* LoadShaper -> LoadRamp
* Initial changes towards load shed confirmatory criteria

**New Feature**:
- Added flow control, load regulation, and concurrency limiting
capabilities
- Updated API definitions, SDKs, blueprints, and policy implementations
- Enhanced documentation for flow control concepts, bundled blueprints,
tutorials, and observability

> 🎉 Flow control's here to stay, 🌊
> Regulating loads, leading the way. ⚖️
> Concurrency limits refined, 🔒
> With docs and blueprints combined! 📚🔧

---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

Update go-swagger (1813)

Description of change

- This update fixes adding descriptions to inner struct fields
- Removed deprecated fields

**Refactor:**
- Removed deprecated fields and updated descriptions for inner struct
fields
- Updated go-swagger package and configurations
- Renamed `BatchPrerolupConfig` to `BatchPrerollupConfig`

**Test:**
- Commented out test cases with TODO message

**Documentation:**
- Updated documentation for various configurations

> 🎉 Deprecated fields, now gone away,
> Descriptions fixed, hooray! 🥳
> Swagger package, up-to-date,
> Configurations celebrate! 🚀

---------

Co-authored-by: Hardik Shingala <hardik.shingalafluxninja.com>

Limit workload latency observations to accepted flows (1814)

Description of change
* Limit workload latency observations to accepted flows with valid
latency.
* Fix invalid signal and flux meter metrics.
* Fix Signals dashboard

**Bug fix:**
- Limit workload latency observations to accepted flows with valid
latency
- Fix invalid signal and flux meter metrics

**Documentation:**
- Correct typo in policy specification documentation

**Chore:**
- Update `prettier` package to the latest version
- Modify build processes for better maintainability

> 🎉 Oh, rejoice! The bugs we've slain, 🐛
> Metrics fixed, no more disdain. 📊
> Docs improved, a typo caught, 📝
> Prettier updated, as it ought. 🌟

---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

Bundle all otel extensions in default agent image (1799)

Agent's default Dockerfile is now enabling all bundled extensions.
Thanks to that, all opentelemetry-collector-contrib-based custom metrics
receivers can be used on default agent image.

Fix feature-rollout dashboards, policy (1801)

Description of change

![Screenshot from 2023-04-24
12-19-21](https://user-images.githubusercontent.com/1553055/234094838-eb4a6d51-ca9a-4ae9-a99f-1cd25868e04b.png)
![Screenshot from 2023-04-24
12-19-39](https://user-images.githubusercontent.com/1553055/234094842-b0cf481f-736d-41e5-aca0-876a97e7b839.png)

**Refactor:**
- Updated Prometheus queries in feature rollout and signals dashboards
- Removed filters and clauses such as `valid="true"` and `by (valid)`
for improved query performance

> 🎉 Oh, the queries we've refined, 📊
> With filters and clauses left behind! 🚀
> Dashboards now lighter, yet still bright, ✨
> Our data shines with newfound might! 💪

Add agent group label to metrics (1800)

**New Feature:**
- Add `AgentGroupLabel` for better agent group identification in metrics
- Update `podCounter` metric, `newAutoScaleControlPoints`, and
`newPodNotifier` functions to support `agentGroup` parameter
- Modify `provideAutoScaleControlPoints` function to include `AgentInfo`
argument and create `PodNotifier` with `AgentGroup` value

> 🎉 A new label takes the stage, 🏷️
> Agent groups now engage. 🤖
> Metrics refined, code aligned, 📊
> Our autoscaling knowledge, we gauge! 🚀

Corrected error messages for namespace scoped installation (1797)

**Bug fix:**
- Improved error handling for forbidden errors in installation utils
- Corrected error messages for better clarity
- Added check for empty endpoints before fetching the controller client
certificate

> 🎉 Oh, rejoice and celebrate! 🥳
> For we've squashed bugs, no more to wait. 🐛
> Error handling now refined, ✨
> And clearer messages we shall find. 📜
> With endpoints checked, we're feeling great! 🚀

Export platform logger constructor so it can be used outside of Fx (1699)


New Feature:
- Added `NewLogger` function for creating logger instances with provided configuration and additional writers
- Modified `provideLogger` function to use the new `NewLogger` method

> 🎉 A logger's tale, so bold and bright,
> With new features, it takes flight.
> Additional writers join the fray,
> As we celebrate this code today! 🚀


---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

support defaults on maps (1790)


SMA Component (1775)

Description of change

- Add Simple Moving Average (SMA) component to the policy language
- Fix rendering boolean type default in docs

Policy dashboard:
![Screenshot from 2023-04-21
11-19-31](https://user-images.githubusercontent.com/1553055/233707796-fb56a3c6-e5dd-4374-b55c-b1b516c8d2b6.png)

Signals dashboard:
![Screenshot from 2023-04-21
11-19-44](https://user-images.githubusercontent.com/1553055/233707779-5bff3940-f744-41e9-898e-3f7234319dfb.png)

**New Feature:**
- Added Simple Moving Average (SMA) filter component to the policy
language

**Documentation:**
- Updated documentation for the new SMA component
- Added default values to agent and controller configuration options

**Style:**
- Removed unnecessary line break in `ema.go`
- Reordered import statements in `logical_test.go`

> 🎉 A new component we bring, 🌟
> The Simple Moving Average, a useful thing! 📈
> With docs updated, users will know, 📚
> How to use it, watch their policies grow! 🌱

---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v1.5.0...releases/aperture-controller/v1.6.0

Page 29 of 53

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.