fix(misconf): fix caching of modules in subdirectories #6814
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Modules are saved and retrieved from the cache by a key, which is built from the module source and version. But when caching a module from a package subdirectory, the relative path of that module is added to the key, which is not taken into account when loading the module from the cache. This leads to two problems:
terraform-aws-modules/s3-bucket/aws//modules/object
andterraform-aws-modules/s3-bucket/aws//modules/notification
, each containing aterraform-aws-modules/s3-bucket/aws
module.terraform-aws-modules/s3-bucket/aws//modules/object
.This PR removes subdirectories from the module source when creating a key, since the package is cached completely.
Doc:
Steps to reproduce:
Checklist