Skip to content

fix: specify clone ID in error message if clone already exists

Artyom Kartasov requested to merge clone-exists-log-entry into master

Description

Specify clone ID in error message if clone already exists

Clone ID is not mentioned in the logs:

2023/06/19 11:54:04 logging.go:16: [INFO]  -> POST /clone
2023/06/19 11:54:04 errors.go:21: [ERROR] [ERROR] - POST /clone - clone with such ID already exists
2023/06/19 11:54:04 util.go:37: [DEBUG] Response: clone with such ID already exists
2023/06/19 11:55:00 logging.go:16: [INFO]  -> GET /status

Related issue

Examples

2023/06/20 01:07:35 logging.go:16: [INFO]   ->  POST /clone
2023/06/20 01:07:35 errors.go:21: [ERROR]  [ERROR] - POST /clone - clone with ID "test1" already exists
2023/06/20 01:07:35 util.go:37: [DEBUG]  Response: clone with ID "test1" already exists

Checklist

  • MR description has been reviewed
  • MR changes are functionally tested
  • MR does NOT have API/CLI changes OR there are API/CLI changes and they have been reviewed & DOCS ARE ADJUSTED (reference doc, etc)
  • MR does NOT have UI changes OR there are UI changes and they have been reviewed & UX IS REVIEWED
Edited by Artyom Kartasov

Merge request reports