Modules that don’t follow provider versioning are likely to face compatibility issues. Currently, our constraints limit the Google provider to google = { version = "~> 4.54" }. However, as the Google APIs evolve with major version changes, sticking to an outdated version could lead to potential breaks or incompatibilities in our modules.
Describe the solution you'd like
A clear and concise description of what you want to happen:
The module should be updated to support the latest major version of the Google provider, specifically version 5. This update will ensure compatibility with the latest API changes and prevent future issues related to outdated dependencies.
How should it work?
The module’s dependency on the Google provider should be updated to reflect the new version, possibly as google = { version = "~> 5.x" } or an appropriate version that ensures compatibility with the new API changes.
Describe alternatives you've considered.
One alternative could be to maintain support for both the current version and the new version of the Google provider. However, this might introduce complexity and potential maintenance challenges.
Additional context
Staying up-to-date with provider versions is crucial for maintaining the reliability and efficiency of our modules. Adapting to major API changes is essential for avoiding future breakdowns and ensuring seamless integration with Google Cloud services.
Is your feature request related to a problem?
Modules that don’t follow provider versioning are likely to face compatibility issues. Currently, our constraints limit the Google provider to google = { version = "~> 4.54" }. However, as the Google APIs evolve with major version changes, sticking to an outdated version could lead to potential breaks or incompatibilities in our modules.
Describe the solution you'd like
A clear and concise description of what you want to happen:
The module should be updated to support the latest major version of the Google provider, specifically version 5. This update will ensure compatibility with the latest API changes and prevent future issues related to outdated dependencies.
How should it work?
The module’s dependency on the Google provider should be updated to reflect the new version, possibly as google = { version = "~> 5.x" } or an appropriate version that ensures compatibility with the new API changes.
Describe alternatives you've considered.
One alternative could be to maintain support for both the current version and the new version of the Google provider. However, this might introduce complexity and potential maintenance challenges.
Additional context
Staying up-to-date with provider versions is crucial for maintaining the reliability and efficiency of our modules. Adapting to major API changes is essential for avoiding future breakdowns and ensuring seamless integration with Google Cloud services.