Here we go again – welcome 1.5.0
The July release aka version 1.5.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: Increased timeout for resource subaccount subscription
Some users might have run into a time-out issue when provisioning a subscription on subaccount level. While this should be a rare case, we provided a quick fix and increased the default timeout for this resource to 60 minutes.
This is a temporal fix, and we will provide a timeout block for the resource in the upcoming release as you already know from environment and service instances.
Feature: Support for subaccount service broker
The new release contains a new resource as well as the corresponding data sources for service brokers on subaccount level.
You find details on how to use them in the documentation:
https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_service_brokerhttps://registry.terraform.io/providers/SAP/btp/latest/docs/data-sources/subaccount_service_brokerhttps://registry.terraform.io/providers/SAP/btp/latest/docs/data-sources/subaccount_service_brokers
Feature: Resource to create roles
While the Terraform provider supported data sources for roles, you could not provision them up to now. With release 1.5.0 we provide a resource that allows you to do exactly that namely provision roles via Terraform on SAP BTP. The resource is available on global account, directory, and subaccount level.
As usual you find the details on parameters and examples in the documentation:
https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/globalaccount_rolehttps://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory_rolehttps://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_role
Fix: Enable creation of duplicate service instances in different environments
You might have run into an issue when trying to service instances with the same name in different environments e.g., one in Cloud Foundry and one on BTP in the runtime “other”.
In case you tried this, you have gotten an error stating “BadRequest”.
We had a small glitch in the data retrieval of the service instance resource that was fixed in this release, so this issue is gone.
Fix: Check for multiple auth parameters
Providing the authentication data for the provider can be done via variables in your configuration or via environment variables. We had some gaps comparing the checks via the provider schema and the injection via environment variables. This would have resulted in “strange” errors messages on your end that were hard to pin down.
These gaps are closed, and the validation now has you covered with meaningful error messages.
Improvement: Improved error handling for entitlement destruction
Sometimes things can go sideways when provisioning or deprovisioning your resources. In these cases, error messages that help you to find the root cause are important.
We are continually improving the provider in this area. An example scenario for this is when you try to destroy an entitlement for which a service instance exists outside of Terraform’s lifecycle.
With this release we added more context to the error message that you get when deleting an entitlement that should help you in investigating the reasons for the issue.
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.3.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 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.5.0The July release aka version 1.5.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: Increased timeout for resource subaccount subscriptionSome users might have run into a time-out issue when provisioning a subscription on subaccount level. While this should be a rare case, we provided a quick fix and increased the default timeout for this resource to 60 minutes.This is a temporal fix, and we will provide a timeout block for the resource in the upcoming release as you already know from environment and service instances.Feature: Support for subaccount service brokerThe new release contains a new resource as well as the corresponding data sources for service brokers on subaccount level.You find details on how to use them in the documentation:https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_service_brokerhttps://registry.terraform.io/providers/SAP/btp/latest/docs/data-sources/subaccount_service_brokerhttps://registry.terraform.io/providers/SAP/btp/latest/docs/data-sources/subaccount_service_brokersFeature: Resource to create rolesWhile the Terraform provider supported data sources for roles, you could not provision them up to now. With release 1.5.0 we provide a resource that allows you to do exactly that namely provision roles via Terraform on SAP BTP. The resource is available on global account, directory, and subaccount level.As usual you find the details on parameters and examples in the documentation:https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/globalaccount_rolehttps://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory_rolehttps://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_roleFix: Enable creation of duplicate service instances in different environmentsYou might have run into an issue when trying to service instances with the same name in different environments e.g., one in Cloud Foundry and one on BTP in the runtime “other”.In case you tried this, you have gotten an error stating “BadRequest”.We had a small glitch in the data retrieval of the service instance resource that was fixed in this release, so this issue is gone.Fix: Check for multiple auth parametersProviding the authentication data for the provider can be done via variables in your configuration or via environment variables. We had some gaps comparing the checks via the provider schema and the injection via environment variables. This would have resulted in “strange” errors messages on your end that were hard to pin down.These gaps are closed, and the validation now has you covered with meaningful error messages.Improvement: Improved error handling for entitlement destructionSometimes things can go sideways when provisioning or deprovisioning your resources. In these cases, error messages that help you to find the root cause are important.We are continually improving the provider in this area. An example scenario for this is when you try to destroy an entitlement for which a service instance exists outside of Terraform’s lifecycle.With this release we added more context to the error message that you get when deleting an entitlement that should help you in investigating the reasons for the issue.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.3.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 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
![Zugriff auf interne Tabellen mit Table Expressions [deutsch]](https://i3.ytimg.com/vi/vMECFG43-EI/hqdefault.jpg)
+ There are no comments
Add yours