v0.10.0

[landscaper]

⚠️ Breaking Changes

• [USER] A type field has been added to import and export definitions in blueprints. To preserve backward compatibility, it is currently optional. However, this is expected to change in the future, therefore it is strongly recommended to treat it as mandatory and always set it. Have a look at the Blueprint documentation for further information. (#224, @Diaphteiros)

✨ New Features

• [OPERATOR] The Landscaper and all internal deployers to now create events for errors that occur. (#233, @schrodit)
• [OPERATOR] A blueprints cache has been introduced in the Landscaper which improves the handling of Blueprints internally. (#229, @schrodit)
  • The Cache size and garbage collection can be configured in the Landscaper configuration.

🐛 Bug Fixes

• [USER] A bug has been fixed that caused the blueprint store to panic when the generated blueprint id exceeded the max allowed characters for a directory name. (#237, @schrodit)
• [USER] A bug has been fixed, that caused a Installation to hang in Progressing state although the corresponding deploy item is already failed. (#234, @schrodit)
  • The state is now correctly propagated and displayed to the user.

🏃 Others

• [DEPENDENCY] The Kubernetes dependencies have been update to v1.21. (#231, @schrodit)
• [DEPENDENCY] The controller-runtime has been update to v0.9.2, including several fixes and a new k8s version support. (#231, @schrodit)
• [DEPENDENCY] The component-spec has been update to v0.0.51. (#231, @schrodit)