-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Configurable timeout for resources #11
Comments
Essential for Kyma Environment |
Additional information: |
Resources that need to be targeted for configurable timeouts (resource + command that needs to be enhanced)
Depends on #293 to have polling implemented consistently |
Additional remark: As we can only specify timeouts but not the |
Work started in branch feat-configurable-timeouts, namely:
|
Hi @lechnerc77 ,
|
Hi @aydin-ozcan, yes this will have impact on all operations (create, delete, ...). Best, |
@aydin-ozcan - FYI: This feature will take a bit more time than expected. In the meantime we changed the timeout for environment instances and services instances from 10 to 60 minutes. The change is available in the new release 0.3.0-beta1 (https://registry.terraform.io/providers/SAP/btp/0.3.0-beta1). |
Thank you @lechnerc77 , this will be suffice for the moment to continue working with the provider . |
Remark for development: currently data sources and resources might reuse the same internal data structure. This needs to be refactored as timeouts are only needed in resources. |
Breaking the customizing down to the two main resources that potentially cause issues:
|
Rebased branch https://github.com/SAP/terraform-provider-btp/tree/feat-configurable-timeouts and added types for data sources of entitlement and service instance without timeout in schema |
After phase 1 the Timeouts in the Terraform provider resources are hard coded. These timeouts should be made configurable.
This also comprises a discussion around SLAs.
The text was updated successfully, but these errors were encountered: