Aperture-py

Latest version: v2.26.0

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

Scan your dependencies

Page 20 of 53

2.12.0rc.1

Changelog

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

Update koanf to v2 (2493)

Release Notes

**Chore**: Updated the `koanf` package to version 2
(`github.com/knadh/koanf/v2`) in `pkg/config/koanf-unmarshaller.go`.
This update enhances configuration management without altering any
existing functionality or interfaces.

> 🎉📦
> A package updated, a chore well done,
> In the world of code, we've had some fun.
> With `koanf` v2, we stride ahead,
> Making strides where others dread.
> No change in function, no cause for alarm,
> Just better config, with its own charm. 🎉📦

Silence the 'lease keepalive response queue is full' warning (2487)

Temporary workaround for https://github.com/fluxninja/cloud/issues/10613
until it's properly fixed.

rename fluxninja cloud to aperture cloud (2481)

Renaming FluxNinja Cloud to Aperture Cloud

Release Notes

Documentation:
- Rebranded the platform from "FluxNinja" to "Aperture" across all
documentation and code comments.
- Updated all references, links, and diagrams in the documentation to
reflect the new name.

Refactor:
- Renamed all instances of "FluxNinja Cloud Controller" to "Aperture
Cloud Controller" in the codebase.
- Updated the `--api-key` option description from "FluxNinja Cloud API
Key" to "Aperture Cloud API Key" across all command-line tools.

> 🎉 Celebrate, for Aperture is here! 🥳
> No more FluxNinja, have no fear. 🚀
> With a new name, we rise anew, 🌅
> To the cloud, we remain true. ☁️
> So let's embrace this change with cheer,
> For a brighter future is near! 🌟

---------

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

Fix temp directory in blueprint generate apply (2480)

Release Notes

Refactor:
- Enhanced the `setupOutputDir` function in
`cmd/aperturectl/cmd/blueprints/generate.go`. It now handles various
scenarios for output directory setup, providing better user interaction
and error handling.

New Feature:
- Introduced case-insensitive user input in `createValuesFile` function
in `cmd/aperturectl/cmd/blueprints/common.go`, improving usability.

> 🎉 Here's to the code that's ever so bright,
> Making changes from morning till night.
> With every refactor, it shines like a star, ✨
> No matter if the users are near or far.
> Case-insensitive, it now stands tall,
> Ready to serve one and all! 🥳

Update documentation to mention grpc/http2 endpoint address (2479)

Release Notes

**Documentation**: Updated the descriptions and instructions for
connecting to FluxNinja Cloud Controller in various configuration files.
The `endpoint` should now be a `grpc/http2` address for cloud
connections, while self-hosted controllers can use `http(s)://`.

> 🎉 Here's to the code that we tweak and refine,
> To make our software truly divine.
> With each PR, we take a step,
> Towards goals that we have adeptly set.
> Today we've made our docs more clear,
> For FluxNinja users far and near.
> So raise your glasses, give a cheer,
> For another successful code review here! 🥂

Make ETCD Client log level configurable (2474)

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

2.11.1

Changelog

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

Fixed the error during the namespace scoped installation (2473)

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v2.11.0...releases/aperture-controller/v2.11.1

2.11.1rc.1

Changelog

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

Fixed the error during the namespace scoped installation (2473)

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

2.11.0

Changelog

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

docs: Rename FluxNinja to FluxNinja Cloud (2470)

Some renames were done earlier, but in few places the product was still
called "FluxNinja".

docs: Document .aperturectl/config better (2463)


docs: Move (FluxNinja) Configuration section to Reference (2435)

Also, document the Cloud Controller under
/reference/fluxninja.mdcloud-controller.

Release Notes

**Documentation:**
- Updated and corrected the links to FluxNinja extension documentation
across multiple files.
- Moved the "FluxNinja Configuration" section to the Reference section
in the documentation.
- Added new information about the FluxNinja Cloud Controller in the
Configuration section.

> 🎉 Here's to the docs that guide our way,
> To the links that were lost but found today.
> With FluxNinja's power now clear to see,
> In the realm of cloud control, we're as happy as can be! 🚀🌟

Provide status of jobs via aperturectl (2431)

**New Feature**: Introduced `aperturectl status`, a new command in
`aperturectl` that allows users to retrieve the status of internal jobs.

Circuit Viz: Display the original config of components using nested circuit (2422)

Release Notes

**Refactor:**
- Introduced a new function `NewNestedCircuitAndOptions` for creating
nested circuits and their options, replacing the previous
`ParseNestedCircuit` function.
- Refactored various component parsing functions to return both a
`runtime.ConfiguredComponent` and a `policylangv1.NestedCircuit`.
- Removed the `name` and `short_description` fields from the
`NestedCircuit` message in the protobuf file.

**New Feature:**
- Added support for arbitrary configuration of nested circuit components
using `google/protobuf/any.proto`.
- Included original configuration of components in nested circuits for
better observability.

**Chore:**
- Updated documentation to reflect changes in the nested circuit
component configuration.

> 🎉 Changes abound, code refactored round,
> Nested circuits now with config found.
> No more name or short description,
> Just pure functionality in this rendition! 🚀

---------

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

Added support to run agent with cloud-controller in playground (2429)

Command to use cloud-controller:

tilt up -- --cloud-controller


Release Notes

**New Feature**: Added support for running the agent with a cloud
controller in the playground. This includes:

- Modifications to flag handling and configuration loading.
- Changes to generate, apply, and delete policies based on provided
parameters.
- Updates to handle cloud controller configurations such as API key,
endpoint, and agent group.

> 🎉 With flags unfurled and settings tweaked,
> In the playground, new paths we've seeked.
> The cloud controller now takes the stage,
> A new chapter begins, turn the page! 🚀

Prevent controller-id generation if cloud controller is enabled (2425)

Modified the `setupControllerInfo` function in `heartbeats.go` and
`provide.go` to prevent the generation of a controller ID when the cloud
controller is enabled. This change hardcodes the ID as "cloud",
simplifying the process and ensuring consistency across the system.

docs: Document Cloud Controller as a default installation method (2424)

- docs: Document Cloud Controller as a default installation method
- remove mention of ARC from playground Tiltfile

Release Notes

**Documentation**: Updated all documentation to reflect the change from
ARC to FluxNinja Cloud Controller as the default installation method.
This includes detailed instructions for installing and configuring the
Aperture Agent with either the FluxNinja Cloud Controller or a
self-hosted Aperture Controller. Also, standardized the capitalization
of "Agents" and "Controller" across all documents for consistency.

> 🎉📚
> With FluxNinja now in sight,
> Our docs shine with newfound light.
> Agents and Controllers stand tall,
> Consistency maintained for all.
> So celebrate this grand revision,
> Born of clarity and precision! 🎉📚

---------

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

docs: Rename FluxNinja ARC to FluxNinja (2423)

**Documentation:**
- Renamed all references to "FluxNinja ARC" to "FluxNinja" and "ARC
Controller" to "FluxNinja Cloud Controller" across the entire codebase,
including documentation, comments, and configuration parameters.

docs: Move controller installation to separate Self-Hosting Aperture section (2419)



[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v2.10.0...releases/aperture-controller/v2.11.0

2.11.0rc.2

Changelog

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

docs: Rename FluxNinja to FluxNinja Cloud (2470)

Some renames were done earlier, but in few places the product was still
called "FluxNinja".

docs: Document .aperturectl/config better (2463)


docs: Move (FluxNinja) Configuration section to Reference (2435)

Also, document the Cloud Controller under
/reference/fluxninja.mdcloud-controller.

Release Notes

**Documentation:**
- Updated and corrected the links to FluxNinja extension documentation
across multiple files.
- Moved the "FluxNinja Configuration" section to the Reference section
in the documentation.
- Added new information about the FluxNinja Cloud Controller in the
Configuration section.

> 🎉 Here's to the docs that guide our way,
> To the links that were lost but found today.
> With FluxNinja's power now clear to see,
> In the realm of cloud control, we're as happy as can be! 🚀🌟

Provide status of jobs via aperturectl (2431)

**New Feature**: Introduced `aperturectl status`, a new command in
`aperturectl` that allows users to retrieve the status of internal jobs.

Circuit Viz: Display the original config of components using nested circuit (2422)

Release Notes

**Refactor:**
- Introduced a new function `NewNestedCircuitAndOptions` for creating
nested circuits and their options, replacing the previous
`ParseNestedCircuit` function.
- Refactored various component parsing functions to return both a
`runtime.ConfiguredComponent` and a `policylangv1.NestedCircuit`.
- Removed the `name` and `short_description` fields from the
`NestedCircuit` message in the protobuf file.

**New Feature:**
- Added support for arbitrary configuration of nested circuit components
using `google/protobuf/any.proto`.
- Included original configuration of components in nested circuits for
better observability.

**Chore:**
- Updated documentation to reflect changes in the nested circuit
component configuration.

> 🎉 Changes abound, code refactored round,
> Nested circuits now with config found.
> No more name or short description,
> Just pure functionality in this rendition! 🚀

---------

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

Added support to run agent with cloud-controller in playground (2429)

Command to use cloud-controller:

tilt up -- --cloud-controller


Release Notes

**New Feature**: Added support for running the agent with a cloud
controller in the playground. This includes:

- Modifications to flag handling and configuration loading.
- Changes to generate, apply, and delete policies based on provided
parameters.
- Updates to handle cloud controller configurations such as API key,
endpoint, and agent group.

> 🎉 With flags unfurled and settings tweaked,
> In the playground, new paths we've seeked.
> The cloud controller now takes the stage,
> A new chapter begins, turn the page! 🚀

Prevent controller-id generation if cloud controller is enabled (2425)

Modified the `setupControllerInfo` function in `heartbeats.go` and
`provide.go` to prevent the generation of a controller ID when the cloud
controller is enabled. This change hardcodes the ID as "cloud",
simplifying the process and ensuring consistency across the system.

docs: Document Cloud Controller as a default installation method (2424)

- docs: Document Cloud Controller as a default installation method
- remove mention of ARC from playground Tiltfile

Release Notes

**Documentation**: Updated all documentation to reflect the change from
ARC to FluxNinja Cloud Controller as the default installation method.
This includes detailed instructions for installing and configuring the
Aperture Agent with either the FluxNinja Cloud Controller or a
self-hosted Aperture Controller. Also, standardized the capitalization
of "Agents" and "Controller" across all documents for consistency.

> 🎉📚
> With FluxNinja now in sight,
> Our docs shine with newfound light.
> Agents and Controllers stand tall,
> Consistency maintained for all.
> So celebrate this grand revision,
> Born of clarity and precision! 🎉📚

---------

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

docs: Rename FluxNinja ARC to FluxNinja (2423)

**Documentation:**
- Renamed all references to "FluxNinja ARC" to "FluxNinja" and "ARC
Controller" to "FluxNinja Cloud Controller" across the entire codebase,
including documentation, comments, and configuration parameters.

docs: Move controller installation to separate Self-Hosting Aperture section (2419)



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

2.11.0rc.1

Changelog

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

docs: Document .aperturectl/config better (2463)


docs: Move (FluxNinja) Configuration section to Reference (2435)

Also, document the Cloud Controller under
/reference/fluxninja.mdcloud-controller.

Release Notes

**Documentation:**
- Updated and corrected the links to FluxNinja extension documentation
across multiple files.
- Moved the "FluxNinja Configuration" section to the Reference section
in the documentation.
- Added new information about the FluxNinja Cloud Controller in the
Configuration section.

> 🎉 Here's to the docs that guide our way,
> To the links that were lost but found today.
> With FluxNinja's power now clear to see,
> In the realm of cloud control, we're as happy as can be! 🚀🌟

Provide status of jobs via aperturectl (2431)

**New Feature**: Introduced `aperturectl status`, a new command in
`aperturectl` that allows users to retrieve the status of internal jobs.

Circuit Viz: Display the original config of components using nested circuit (2422)

Release Notes

**Refactor:**
- Introduced a new function `NewNestedCircuitAndOptions` for creating
nested circuits and their options, replacing the previous
`ParseNestedCircuit` function.
- Refactored various component parsing functions to return both a
`runtime.ConfiguredComponent` and a `policylangv1.NestedCircuit`.
- Removed the `name` and `short_description` fields from the
`NestedCircuit` message in the protobuf file.

**New Feature:**
- Added support for arbitrary configuration of nested circuit components
using `google/protobuf/any.proto`.
- Included original configuration of components in nested circuits for
better observability.

**Chore:**
- Updated documentation to reflect changes in the nested circuit
component configuration.

> 🎉 Changes abound, code refactored round,
> Nested circuits now with config found.
> No more name or short description,
> Just pure functionality in this rendition! 🚀

---------

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

Added support to run agent with cloud-controller in playground (2429)

Command to use cloud-controller:

tilt up -- --cloud-controller


Release Notes

**New Feature**: Added support for running the agent with a cloud
controller in the playground. This includes:

- Modifications to flag handling and configuration loading.
- Changes to generate, apply, and delete policies based on provided
parameters.
- Updates to handle cloud controller configurations such as API key,
endpoint, and agent group.

> 🎉 With flags unfurled and settings tweaked,
> In the playground, new paths we've seeked.
> The cloud controller now takes the stage,
> A new chapter begins, turn the page! 🚀

Prevent controller-id generation if cloud controller is enabled (2425)

Modified the `setupControllerInfo` function in `heartbeats.go` and
`provide.go` to prevent the generation of a controller ID when the cloud
controller is enabled. This change hardcodes the ID as "cloud",
simplifying the process and ensuring consistency across the system.

docs: Document Cloud Controller as a default installation method (2424)

- docs: Document Cloud Controller as a default installation method
- remove mention of ARC from playground Tiltfile

Release Notes

**Documentation**: Updated all documentation to reflect the change from
ARC to FluxNinja Cloud Controller as the default installation method.
This includes detailed instructions for installing and configuring the
Aperture Agent with either the FluxNinja Cloud Controller or a
self-hosted Aperture Controller. Also, standardized the capitalization
of "Agents" and "Controller" across all documents for consistency.

> 🎉📚
> With FluxNinja now in sight,
> Our docs shine with newfound light.
> Agents and Controllers stand tall,
> Consistency maintained for all.
> So celebrate this grand revision,
> Born of clarity and precision! 🎉📚

---------

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

docs: Rename FluxNinja ARC to FluxNinja (2423)

**Documentation:**
- Renamed all references to "FluxNinja ARC" to "FluxNinja" and "ARC
Controller" to "FluxNinja Cloud Controller" across the entire codebase,
including documentation, comments, and configuration parameters.

docs: Move controller installation to separate Self-Hosting Aperture section (2419)



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

Page 20 of 53

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.