Skip to content

[Feature Request] Subscription Manager instance creation dependency issue  #197

Description

@mpechkurov

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.

  1. Prepare yaml file with the service Identity Service, Saas registry, Subscription Manager.
  2. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/mediumFeature is broken, workaround available

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Closed
    Status
    Closed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions