v0.6.0

Release notes for Enforcement 0.6.0

This version makes Enforcement more flexible, allowing the creation of cluster rules with dynamic configuration and the implementation of triggers that will be activated before and after each package installation. Triggers allow external applications to be notified of installation events.
This version also includes some improvements in the integration with ArgoCD.

Significant changes:

• Trigger BeforeInstall and AfterInstall;
• Dynamic configuration;
• Integration optimizations with ArgoCD;

Breaking changes

This release requires an update to the Custom Resource Definition.
The current version can be found here.

v0.5.1

Release notes for Enforcement 0.5.1

This release fixes an issue encountered when multiple clusterrules share the same resources and a cluster eviction event is detected.

Significant changes:

• Error deleting resources;

v0.5.0

Release notes for Enforcement 0.5.0

This version evolves the project to allow other sources of clusters to be supported in the future, making the credentials of each cluster source read through secrets. A modification was also made to the rancher's cluster source in order to better identify the events captured through the API.

Significant changes:

• Change Rancher Source cluster search strategy;

Breaking changes

• Configuration secrets for cluster sources;

v0.4.1

Release notes for Enforcement 0.4.1

Fixing the cluster status check and fixing the versions of the Enforcement dependencies

Significant changes:

• Fixed cluster status check.

v0.4.0

Release notes for Enforcement 0.4.0

This version contains improvements made to the project. Unit tests were implemented at the domain layer and a more robust error handling.

Significant changes:

• Log Warning .
• Unit Tests .
• Improve Error Handling .

v0.3.0

Release notes for Enforcement 0.3.0

This version contains small new features added to the project.

Significant changes:

• Creation of projects .

v0.2.0

Release notes for Enforcement 0.2.0

This version contains significant changes made to the project. Architectural and behavioral changes were made. This version breaks compatibility with the previous version and defines the project's operating strategy.

Significant changes:

• Transformation of Enforcement into a Kubernetes operator;
• Creation of a custom resource definition to specify enforcements and a matching rule for clusters filtered at the source;
• Architectural refactoring;
• Structural change to allow the inclusion of new cluster sources in addition to Rancher.

Breaking changes

• Support for the default repository defined in version 0.1.0 has been removed;
• The cluster_ignore configuration is now reported in the custom resource.

v0.1.0

Initial version of the project.