Christian Lechner

@ThomasVitale I think this section is good to go and the content can be merged into the final document.

+100 : Keeping track and follow-up in a structured way via GH issues is imho the perfect approach. Would be also great to have them in a dedicated GH project...

@FlorianL-Git as you pointed out, the operation of moving an account is an imperative operation and intentionally did not model in the Terraform provider. From our current experience this should...

## Community Note ### Voting for Prioritization * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original post to help the community and maintainers prioritize this...

First step: Evaluate BTP CLI commands to understand the semantics also compared to the actions you can do the the SAP BTP cockpit

## Starting point After the creation of a subaccount one default key is already existing. This means that if further config option (currently not available, will be made available) an...

@MarcusNotheis we are working on providing a dedicated resource for destinations as proposed in you feature request. As this is not only a topic of the Terraform provider, some pre-work...

@CoKueb I will ping you. However the functionality must be added first the BTP CLI before we can use it in the provider

@ptesny : I agree that the provisioning via service instances works. However, this is not the preferred way from the perspective of destinations and comes with some short comings (no...

Hi @Zearom , **disclaimer** first: the following statements are the **plan**, but we cannot guarantee that the mentioned timelines might not change. Though the risk for severe changes is low,...