Consistently use the preferences and history names in the bff code base - Part 2 43/135843/1
authorFiete Ostkamp <Fiete.Ostkamp@telekom.de>
Tue, 29 Aug 2023 07:34:06 +0000 (09:34 +0200)
committerFiete Ostkamp <Fiete.Ostkamp@telekom.de>
Tue, 29 Aug 2023 07:35:26 +0000 (09:35 +0200)
commitafe2aaffdd5679e61f27f7b5597b21db6a8db4e0
treee6221a8a1f708332c0afeb1cf0634ba46419096a
parent4b7cd5405dea9003f31af1aa9cd584d8ccf2141f
Consistently use the preferences and history names in the bff code base - Part 2

- some history related properties still had a portal prefix

Issue-ID: PORTALNG-50
Change-Id: Ia044b42c306b8a8837d1cda92f101aebe62283a1
Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
app/src/main/resources/application-development.yml
app/src/main/resources/application.yml
app/src/test/java/org/onap/portalng/bff/actions/CreateActionsIntegrationTest.java
app/src/test/java/org/onap/portalng/bff/actions/ListActionsIntegrationTest.java
development/.env
development/docker-compose.yml
lib/src/main/java/org/onap/portalng/bff/config/clients/HistoryConfig.java
lib/src/main/java/org/onap/portalng/bff/services/ActionService.java
openapi/server/src/main/resources/static/api.yaml