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
feat(terraform): rework dep types #9116
Conversation
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
@@ -1,19 +1,36 @@ | |||
Currently Terraform support is limited to Terraform registry sources and github sources that include SemVer refs, e.g. like `github.com/hashicorp/example?ref=v1.0.0`. | |||
Currently, Terraform supports renovating the following dependencies, where sub points represent hosting options of the dependencies: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, Terraform supports renovating the following dependencies, where sub points represent hosting options of the dependencies: | |
Terraform supports renovating the following dependencies, where sub points represent hosting options of the dependencies: |
To me the use of the words "Currently, " implies that on a later date Renovate/Terraform will support more renovations. By not using such words as "currently, later, right now, in future" we don't create expectations of further improvements. The sentence would read just as nice if we removed the word "Currently, ".
Also by not using words like "Currently" we free ourselves from updating the docs when at a later time "Currently, Terraform supports..." some other renovation as well.
So overall, I think using "time-based" language like this is a bit dangerous.
But let's see what the rest of the Renovate team thinks about using words like this in our docs...
So don't rush into applying this suggestion right away, as I'm curious what the rest of the Renovate team has to say. Maybe I'm totally honking up the wrong pond here... 😄
FYI I'm marking all breaking change PRs as draft to reduce the chance of accidental merge |
@secustor I seem to have broken this in the merge. Could you take a look? |
@rarkins Seems like a new test has been added, fixed the snapshot. |
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Improves the `depType` values returned by the terraform manager. Closes #8792 BREAKING CHANGE: Values for extracted `depType` in terraform manager have changed, please see the `terraform` manager readme for details.
Changes:
This PR changes all
depTypes
provided by the Terraform manger to allow a more fain grained control over which dependencies are updated and which are not.Context:
Closes #8792
I'm not sure how to do the migration for users which use the
helm
depType.Can you point me to some example PR where this has already been done?
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: