Support for destinations instead of service binding

[PascalEvertzLeo]

Hi,

as of now, this useful plugin can only be used, if dms instance is in the same account and space, as the actual cap app.

Is there a plan to support destinations instead of direct service binding ? Since the dms instance and the cap app(s), might not reside in the same subaccount/space that would be a very useful addition.

Thanks and BR
Pascal

[dheerasameerk]

Hi @PascalEvertzLeo,

May I know what is the reason to not have a service instance of dms in the same subaccount as you cap application? You might have created a dms service instance in another subaccount but do you see any challenges to create a new one and it and the cap app in same subaccount?

[PascalEvertzLeo]

Hi @dheerasameerk ,

the reason is, that the dms instance (and the repositories, that reside in it) should be shared across different subaccounts and spaces. For example having a central service subaccount and other subaccounts for different business units or projects.

The only technical possibility that i know of, is to integrate the repository to other subaccounts/spaces via destination. And if the sdm plugin would support this, it would be capable of supporting a central reuse repository.

[iocast]

@dheerasameerk are there any plans regarding this issue?

[yashmeet29]

Hi @iocast, @PascalEvertzLeo ,

We have made a note of this and since we do not have capacity right now, we will prioritise this in our roadmap based on capacity.

Regards,
Yashmeet