digiwf-core
digiwf-core copied to clipboard
Align properties
Is your feature request related to a problem? Please describe.
As an administrator of DigiWF, I gain better clarity when properties are named consistently. The following properties should be renamed so that they no longer contain package names but instead begin with digiwf.
Describe the solution you'd like
Properties that start with io.muenchendigital.digiwf or de.muenchen.oss.digiwf should be renamed to start with digiwf only.
Findings are: io.muenchendigital.digiwf.mail.* de.muenchen.oss.digiwf.address. service.url de.muenchen.oss.digiwf.connector.core.integrations.* io.muenchendigital.digiwf.alw.personeninfo.* io.muenchendigital.digiwf.cosys.* io.muenchendigital.digiwf.message.* de.muenchen.oss.digiwf.dms.supported-file-extensions.* io.muenchendigital.digiwf.mail.* de.muenchen.oss.digiwf.okewo.* de.muenchen.oss.digiwf.ticketing.supported-file-extensions.* io.muenchendigital.digiwf.streaming.typeMappings.correlatemessagev01
Describe alternatives you've considered
Properties remain as they are.
Acceptance Criteria
Properties are aligned in the following components within the application*.yaml files, in the properties and configuration classes both in the production code and in the test code, as well as in the ops repository:
- [ ] engine
- [ ] connector
- [ ] address-integration
- [ ] cosys-integration
- [ ] dms-integration
- [ ] email-integration
- [ ] example-integration
- [ ] okewo-integration
- [ ] openai-integration
- [ ] ticket-integration
- [ ] s3-integration-client-example
Additional context