You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The attributes provided by data.ibm_database_connection should also be provided by ibm_database.
Because they are not, we have to use both ibm_database and data.ibm_database_connection and the resources that depends on data.ibm_database_connection get recreated each time there is a potential change in ibm_database, leading to data.ibm_database_connection stating "will be read during apply, depends on a resource or a module with changes pending".
Community Note
Description
The attributes provided by
data.ibm_database_connection
should also be provided byibm_database
.Because they are not, we have to use both
ibm_database
anddata.ibm_database_connection
and the resources that depends ondata.ibm_database_connection
get recreated each time there is a potential change inibm_database
, leading todata.ibm_database_connection
stating "will be read during apply, depends on a resource or a module with changes pending".This is a well known issue when attributes are only available from data sources, see hashicorp/terraform-provider-aws#29421 (comment)
The solution is to provide all attributes of
data.ibm_database_connection
onibm_database
so that the resource is enough to get the connection info.New or Affected Resource(s)
The text was updated successfully, but these errors were encountered: