Another month, another release - welcome 1.2.0
The April release aka version 1.2.0 of the Terraform provider for SAP BTP is out. Let’s look at what has been added since the last release.
Of course, you also find all the information in the release notes in the GitHub repository:
Let us do a short walk through the new features in the next sections. By the way: the new features have been requested by you the community. So, keep the requests coming.
Feature: Get Subaccount Data by subdomain and region
One feature request filed in the “early days” of the Terraform provider was that the consistency between the creation of a subaccount resource and the corresponding data source. The missing piece was that later was not capable of reading a subaccount based on the subdomain and the region.
With this release we now closed the gap, so besides fetching the data via the subaccount ID you can now also read the subaccount data by providing the region and the subdomain of the subaccount as shown in the following screenshots with the code and the result of the execution:
Feature: Ability to share service instances
One requested feature was to enable the functionality to share service instances if the service plan allows.
With release 1.2.0 this feature is now supported:
- You can now check if a service plan supports the instance sharing
- You can create and update service instance with instance sharing enabled or disabled
Bringing this together:
This results in:
Fix: Creation of Service Binding
The creation of some service bindings (like for the cloud logging service) caused a crash in the Terraform provider for SAP BTP. The reason for this was a non-uniform response of the REST calls that trigger the creation. With release 1.2.0 we got you covered and made the call more resilient to avoid this crash.
If you are facing this issue, please upgrade to version 1.2.0.
Fix: Parameters of Kyma example
We had a little glitch in our examples for creating environments namely in the case when creating a Kyma environment. The key of the JSON parameters had the wrong format. This is fixed and you can use the code of the example successfully now. You find the examples here: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_environment_instanc...
How to update?
The update of the provider version is straightforward. Depending on your configuration in the provider, you must adjust the version constraint to 1.2.0 and execute a “terraform init -upgrade”.
That’s it.
To improve the stability of the provider we are now also starting to integrate the Discovery Center missions available in our samples repository (https://github.com/SAP-samples/btp-terraform-samples) into our test workflows. This way we also cover more complex scenarios and this way improve the stability of the provider.
You find the documentation of the enhanced resources in the Terraform registry: https://registry.terraform.io/providers/SAP/btp/latest
Feedback, questions, bugs, feature requests
The procedure hasn’t change: if you want to interact with us, use the GitHub repository https://github.com/SAP/terraform-provider-btp:
- To file a bug, please open an issue in the repository.
- To file a feature request, please file it in the repository.
- If you have a question, want to discuss ideas or do some “show & tell”, feel free to start a GitHub Discussion.
There are also some feature requests open that you can vote for. Check for the issues that are label as “enhancement” and “pending decision“ via this link https://github.com/SAP/terraform-provider-btp/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement+labe... .
What’s next?
Do you want a sneak peek what is coming next and when we plan to deliver a next release? You find that information in the milestones on our GitHub repository https://github.com/SAP/terraform-provider-btp/milestones
Be aware that plans and dates might change through the course of development.
One more thing …
One big topic is the import of existing resources and bringing them under the management of Terraform. This is already possible today with the mechanisms Terraform provides, but this is also quite some work to do on your end.
We want to make this process much easier for you and are working on an exporting functionality that allows you to export the resources of a subaccount in one batch. The working title is BTP Terraform Exporter and the progress is documented in the issue https://github.com/SAP/terraform-provider-btp/issues/724.
This is a quite a bit to develop, but we see this as an essential part of enabling your journey towards Terraform on SAP BTP.
With that … happy Terraforming!
- SAP Managed Tags:
