Context propagation for InstanceManager Status and Delete 13/142713/1
authorFiete Ostkamp <fiete.ostkamp@telekom.de>
Tue, 9 Dec 2025 09:46:09 +0000 (10:46 +0100)
committerFiete Ostkamp <fiete.ostkamp@telekom.de>
Tue, 9 Dec 2025 09:51:07 +0000 (10:51 +0100)
commitcac9e449baeab15bf88df7b12007de4cc49fdcd7
treefca5767533456b048e700f00a5c0902942a3faf9
parenta96b6a14c6dd29dc340a474a060a1ac27c79dcda
Context propagation for InstanceManager Status and Delete

- enhance the Status and Delete methods of the InstanceManager
  interface to require the context paramater
- this is done to validate the approach and see if the handler
  and db related spans are then connected in one trace
- the other methods of the interface will follow once that works [0]

[0] this is also done because the diff of changes would become quite large
    if everything would be changed at once

Issue-ID: MULTICLOUD-1538
Change-Id: Ia1ec590f3326773e0df1e6cefba97711975bbf48
Signed-off-by: Fiete Ostkamp <fiete.ostkamp@telekom.de>
src/k8splugin/api/brokerhandler.go
src/k8splugin/api/instancehandler.go
src/k8splugin/api/instancehandler_test.go
src/k8splugin/go.mod
src/k8splugin/internal/app/instance.go
src/k8splugin/internal/app/instance_test.go
src/k8splugin/internal/app/subscription.go