You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request]: Allow merging of multiple config files #704
Is your feature request related to a problem? Please describe.
In many projects, including now our own, one sees two or three different YAML configurations for UI5, each doing a different thing (one running with the mockserver middleware, a different one with the fiori local middleware &c.), but all sharing a lot of common information.
I would like to be able to run e.g. ui5 serve --config ui5.yaml --config mockserver.yaml and have the two config files effectively merged into one configuration.
Describe alternatives you've considered
catting the config files together and passing it to ui5, but besides being wonky, the UI5 CLI doesn't support passing configuration on stdin
pasting the two configs into a new file using a pre-run NPM script, passing that to ui5 serve, deleting it afterwards (also not great)
Thanks for filing this feature request. Am I understanding it correctly that the two files contain configuration for the same project (the application)?
A ui5.yaml file can contain multiple configurations (e.g. multiple projects, extensions, etc), so we need to be careful which configurations should be merged.
Hello @RandomByte, that is correct! I understand further thought needs to be given to the question you mention, when one has multiple documents/configuration in a single document, but perhaps the most straightforward solution could be not to support this case (i.e. return an error when one of the files to be merged contains multiple YAML documents) and only allow merging of single-document files?
To merge multiple documents, the metadata.name could be used as key to identify the right document.
I would at least expect those fields (specVersion, metadata, type) to be mandatory (also to be able to use the schema validation).
Activity
RandomByte commentedon Dec 6, 2022
Thanks for filing this feature request. Am I understanding it correctly that the two files contain configuration for the same project (the application)?
A
ui5.yamlfile can contain multiple configurations (e.g. multiple projects, extensions, etc), so we need to be careful which configurations should be merged.jakubledl commentedon Jan 3, 2023
Hello @RandomByte, that is correct! I understand further thought needs to be given to the question you mention, when one has multiple documents/configuration in a single document, but perhaps the most straightforward solution could be not to support this case (i.e. return an error when one of the files to be merged contains multiple YAML documents) and only allow merging of single-document files?
matz3 commentedon Jan 4, 2023
To merge multiple documents, the
metadata.namecould be used as key to identify the right document.I would at least expect those fields (specVersion, metadata, type) to be mandatory (also to be able to use the schema validation).