-
Bug
-
Resolution: Fixed
-
Major
-
5.4
-
None
-
-
Empty show more show less
-
Yes
-
Basel 42
-
8
POC exists in FORGE/light-yaml. Since POC contains more than just solution for this issue, for the task itself we need to:
- extract just the solution
- extract and adapt relevant test
- review & QA
- time overhead introduced by the solution (document it either in resolution comment if negligible or in release notes & documentation on yaml loading if more significant)
Original description:
In YAML configuration files we support includes of other YAML files. The problem is that changes in an included file will not trigger the observation based releasing of the complete configuration. Some developers workaround with fake edits in the including file by adding a space for instance.
Note: in development mode we might want to load the YAML configuration on each request of the provider to avoid any stall configuration.
- depends upon
-
MAGNOLIA-6223 Provide proper API for resource change communication
- Closed
-
MAGNOLIA-6649 Refactor NameDefinition <-> DefinitionMetadata name binding mechanism
- Closed
-
MAGNOLIA-6650 Let DefinitionProvider report the last modification date
- Closed
- is causing
-
MAGNOLIA-6671 Unexpected exception log statements when queried definition is backed by an empty YAML file
- Closed
- relates to
-
MAGNOLIA-6672 Exceptions after YAML defined template is removed
- Closed
-
MAGNOLIA-6342 YAML config files are not automatically refreshing
- Closed
-
MAGNOLIA-6494 Create log messages when FileSystemResource(s) are reloaded
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...