breaking: Rework depTypes of the Terraform manager

[secustor]

What would you like Renovate to be able to do?

To allow a more fine grained control over the behavior of the Terraform manager a rework of the used depType values is needed.
For example it should be possible to deactivate the renovating of required providers or the required Terraform version.

Context: #8746 (comment)

Did you already have any implementation ideas?

If I understand the underlying mechanics correctly, depType has no longer any affects outside of text rendering as long as a data source is provided.

ressource	suggested depType	current value	datasources used
terraform provider	provider	terraform	terraform-provider
required terraform provider	required_provider	terraform	terraform-provider
required terraform version	required_version	terraform	github-tags
terraform module	module	terraform, github, gitTags	terraform-module, github-tags, git-tags
helm release	helm_release	helm	helm
docker container	docker_container	stage, final (inherited from Dockerfile manager)	docker ( inherited )
docker image	docker_image	stage, final (inherited from Dockerfile manager)	docker ( inherited )
docker service	docker_service	stage, final (inherited from Dockerfile manager)	docker ( inherited )

[rarkins]

Can you edit the above table to include what the existing depType value is for each case?

And we should keep in mind that the purpose of depType is not to duplicate datasource, it's to distinguish between different types of dependencies when datasource alone is not enough. The above list looks pretty good though, e.g. the various docker_ types.

[github-actions]

This issue has been labeled with status:requirements. This indicates that we don't know enough to start work and further requirements or a reproduction are needed first.

This label will be replaced with status:ready once all requirements and reproductions necessary to start work have been met.

If it's not clear what is missing to move this issue forward, ask for clarification in a new comment. If you think we already have what we need to move forward, mention this in a new comment.

[secustor]

I have added a current-value and data source column to get a better oversight of the current setup.

The only sub-type which could be dropped in my opinion is the helm-release depType.
IMHO it would be beneficial to add a depType in that case too. This could be the case, if Renovate provides additional functionality which could collide here.
For example migrations for helm repos and the user in that case maybe prefers to only update the repo but not the version.

[rarkins]

Which of the current values do you think people might be using in packageRules and which of those do you think we can migrate automatically? If we can do that then it reduces most of the "breaking" nature.

[secustor]

The only depType where it is making sense to do package rules right now are helm and the Docker ones.

Helm is easy to migrate and Docker should more of a niche to handle with Terraform.

[secustor]

@rarkins Are you missing still any requirements?
I think we have everything to start the implementation.

[renovate-release]

🎉 This issue has been resolved in version 25.0.0 🎉

The release is available on:

• GitHub release
• 25.0.0

Your semantic-release bot 📦🚀