RELEASED: Public: 2022-04-06
New features
- Added the CLI command to validate bundles in operations center (BEE-10530)
-
When a bundle is added to the operations center using the Configuration as Code bundle location, it can be validated using a new CLI command.
The CLI output provides information about the following:
-
General validation messages in the files and folders of the bundle.
-
Specific validation messages on every online controller where the bundle is applied.
-
List of all offline controllers where the bundle is applied, but the validation did not occur because of the controller’s status.
-
- Added HTTP endpoint to validate bundles in operations center (BEE-10530)
-
When a bundle is added to the operations center using the Configuration as Code bundle location, it can be validated using a new HTTP endpoint.
The output provides information about the following:
-
General validation messages in the files and folders of the bundle.
-
Specific validation messages on every online controller where the bundle is applied.
-
List of all offline controllers where the bundle is applied, but the validation did not occur because of the controller’s status.
-
Feature enhancements
- Allow bundle to accept only one entry for a plugin catalog (BEE-14831)
-
When there are multiple plugin catalog files in a bundle, a log message is generated to tell you which file is effectively used.
Resolved issues
- The 'DescriptorValidator' invocation was missing on the bundle synchronization (BEE-16142)
-
When bundles were loaded, the bundle synchronization was missing the bundle descriptor validator that checks the mandatory fields and sections information.
This issue was resolved and the validation is now properly performed.
-
Internal changes to streamline development. Not user visible. (BEE-15780)
-