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 }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Describe the bug
POST endpoint in SettingsResource aside from creating new records also overwrites existing ones. There should be some check for duplicates.
To Reproduce
Steps to reproduce the behavior:
Create new Setting through REST request
Send the same request second time (optionally try to change some value to see the change)
Go to Settings table in DB and see that record has been changed
Expected behavior
POST endpoint should only create new records. It should not be able to update them.
Observed behavior
SettingsResource#POST request overwrites existing settings records
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
I already commented on this here: #164
The implementation of saveConfigurationSetting method from OperatorServiceBean class in the oscm repository and the ConfigurationKey class from oscm-interfaces need refactoring in order to make the POST endpoint work correctly.
I edited the task name.
Crystalzord
changed the title
Setting#POST enpoint overwrites existing setting records
Reimplement Setting#POST endpoint
Dec 9, 2019
Describe the bug
POST endpoint in SettingsResource aside from creating new records also overwrites existing ones. There should be some check for duplicates.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
POST endpoint should only create new records. It should not be able to update them.
Observed behavior
SettingsResource#POST request overwrites existing settings records
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: