Here we go again – welcome 1.6.0
Another month has passed, and I hope you had a great summer vacation. And as another month has passed, say welcome to the August release aka version 1.6.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:
Feature: Add timeout block for subaccount subscription
Up to now you had the option to configure timeouts for environments and service instances to avoid running into timeouts during the execution of your Terraform script.
We got the feedback that this is also needed for the resources of subscriptions. So here you go. With this release you can also define a timeout block when defining subscriptions in Terraform.
If you are already using this resource type, no worries, the change is backward compatible, so no changes needed in your existing configurations. They will behave the same as in the prior releases.
Feature: Add dashboard URL to service instance
Due to community feedback, we have been made aware that the field “dashboard_url” is missing as read-only attribute and this would be quite handy to have this. Well, with release 1.6.0 you have now also access to this field when creating the resource.
The documentation was updated accordingly: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_service_instance
Feature: Add retry logic for rate limit for entitlement
Some of our users reported that they ran into issues when setting up entitlements for bigger landscapes in CI/CD pipelines, so not only a lot of entitlements but also an execution in parallel. Due to many calls to the platform API triggered via the provider, the system ran into a rate limit error.
This error was propagated and consequently the execution of the Terraform run was aborted.
With release 1.6.0 we enhanced the implementation for entitlements to react a bit more sophisticated when an according error is raised by the underlying API. In detail the processing will not be aborted, but a retry loop is triggered. This should mitigate the issue of running into a rate limit-
Feature: Resource to manage XSUAA API Credentials
As you might know the Terraform provider for SAP BTP stands on the shoulder of the giant BTP CLI (BTP CLI server to be precise). The BTP CLI commands evolve and consequently we must then do the necessary adoptions on the Terraform side to get the new commands in as resources.
This release contains the results of the exercise for the BTP CLI command “security/api-credential” (https://help.sap.com/docs/btp/btp-cli-command-reference/security-api-credential). Version 1.6.0 contains the corresponding resources. You find all the details in the documentation:
Global Account: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/globalaccount_api_credentialDirectory: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory_api_credentialSubaccount: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_api_credential
Fix: data source subaccount – empty placeholders in error message
Due to a glitch in the data source subaccount the error message template that was raised due to a wrong configuration was empty and one might say not a very big help for you to pin down the error in your Terraform configuration.
With release 1.6.0 the error template gets filled correctly and the error message now helps you in pinning down the issue as you would expect it.
How to update?
I guess you already know the drill, but anyhow. The update of the provider version is straightforward. Depending on your configuration in the provider, you must adjust the version constraint to 1.6.0 and execute a “terraform init -upgrade”.
That’s it.
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+label%3Apending-decision.
What else?
You are certainly aware that we are also working on a Terraform provider for Cloud Foundry that you find here https://github.com/SAP/terraform-provider-cloudfoundry. The provider has already a quite mature state and the first release candidate is out. A Expect to see an update (a GA version???) around TechEd (I guess they call it “event-driven delivery” ;-)).
We are also working on the functionality to make your life easier when it comes to do the Terraform import for landscapes (working Title Terraform Exporter) as described in this issue https://github.com/SAP/terraform-provider-btp/issues/724. We are making very good progress, so I hope to share some news soon.
What is next?
Do you want a sneak peek at what is coming next and when we plan to deliver the 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.
With that … happy Terraforming!
Here we go again – welcome 1.6.0Another month has passed, and I hope you had a great summer vacation. And as another month has passed, say welcome to the August release aka version 1.6.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:Feature: Add timeout block for subaccount subscriptionUp to now you had the option to configure timeouts for environments and service instances to avoid running into timeouts during the execution of your Terraform script.We got the feedback that this is also needed for the resources of subscriptions. So here you go. With this release you can also define a timeout block when defining subscriptions in Terraform.If you are already using this resource type, no worries, the change is backward compatible, so no changes needed in your existing configurations. They will behave the same as in the prior releases.Feature: Add dashboard URL to service instanceDue to community feedback, we have been made aware that the field “dashboard_url” is missing as read-only attribute and this would be quite handy to have this. Well, with release 1.6.0 you have now also access to this field when creating the resource.The documentation was updated accordingly: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_service_instanceFeature: Add retry logic for rate limit for entitlementSome of our users reported that they ran into issues when setting up entitlements for bigger landscapes in CI/CD pipelines, so not only a lot of entitlements but also an execution in parallel. Due to many calls to the platform API triggered via the provider, the system ran into a rate limit error.This error was propagated and consequently the execution of the Terraform run was aborted.With release 1.6.0 we enhanced the implementation for entitlements to react a bit more sophisticated when an according error is raised by the underlying API. In detail the processing will not be aborted, but a retry loop is triggered. This should mitigate the issue of running into a rate limit-Feature: Resource to manage XSUAA API CredentialsAs you might know the Terraform provider for SAP BTP stands on the shoulder of the giant BTP CLI (BTP CLI server to be precise). The BTP CLI commands evolve and consequently we must then do the necessary adoptions on the Terraform side to get the new commands in as resources.This release contains the results of the exercise for the BTP CLI command “security/api-credential” (https://help.sap.com/docs/btp/btp-cli-command-reference/security-api-credential). Version 1.6.0 contains the corresponding resources. You find all the details in the documentation:Global Account: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/globalaccount_api_credentialDirectory: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory_api_credentialSubaccount: https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_api_credentialFix: data source subaccount – empty placeholders in error messageDue to a glitch in the data source subaccount the error message template that was raised due to a wrong configuration was empty and one might say not a very big help for you to pin down the error in your Terraform configuration.With release 1.6.0 the error template gets filled correctly and the error message now helps you in pinning down the issue as you would expect it.How to update?I guess you already know the drill, but anyhow. The update of the provider version is straightforward. Depending on your configuration in the provider, you must adjust the version constraint to 1.6.0 and execute a “terraform init -upgrade”.That’s it.You find the documentation of the enhanced resources in the Terraform registry: https://registry.terraform.io/providers/SAP/btp/latestFeedback, questions, bugs, feature requestsThe 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+label%3Apending-decision.What else?You are certainly aware that we are also working on a Terraform provider for Cloud Foundry that you find here https://github.com/SAP/terraform-provider-cloudfoundry. The provider has already a quite mature state and the first release candidate is out. A Expect to see an update (a GA version???) around TechEd (I guess they call it “event-driven delivery” ;-)). We are also working on the functionality to make your life easier when it comes to do the Terraform import for landscapes (working Title Terraform Exporter) as described in this issue https://github.com/SAP/terraform-provider-btp/issues/724. We are making very good progress, so I hope to share some news soon. What is next?Do you want a sneak peek at what is coming next and when we plan to deliver the 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.With that … happy Terraforming! Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
