Describe the bug
Subscription Manager instance creation requires 2 additional instance of Identity Service and Saas registry.
Input/creation payload required name of this instances and instance should be created before.
Tested with Provider Version
v0.3.3
To Reproduce
Steps to reproduce the behavior:
Prerequisites: BTP and CF created.
- Prepare yaml file with the service Identity Service, Saas registry, Subscription Manager.
- Apply yaml configuration
Expected behavior
3 services created
Actual behavior
2 services created but the service which depends on another two stuck in the loop
Additional context
It should be the option in the service creation to mark service depends on another service
- so service can wait for another required services
- also should check before deletion if the dependent service still exists
Describe the bug
Subscription Manager instance creation requires 2 additional instance of Identity Service and Saas registry.
Input/creation payload required name of this instances and instance should be created before.
Tested with Provider Version
v0.3.3
To Reproduce
Steps to reproduce the behavior:
Prerequisites: BTP and CF created.
Expected behavior
3 services created
Actual behavior
2 services created but the service which depends on another two stuck in the loop
Additional context
It should be the option in the service creation to mark service depends on another service