fix(core): potential edge-case issue with versions and generateFiles

This is a little bit of a shot in the dark, looking to solve an issue
reported on Slack
(https://kubernetes.slack.com/archives/CKM7CP8P9/p1614599864049600), but
it's in any case a sane thing to do. Basically we now ensure that a new
tree scan is performed after manipulating files in a particular module
path.

core/src/resolve-module.ts

@@ -27,6 +27,7 @@ import Bluebird from "bluebird"
 import { readFile, mkdirp, writeFile } from "fs-extra"
 import { LogEntry } from "./logger/log-entry"
 import { ModuleConfigContext } from "./config/template-contexts/module"
+import { pathToCacheContext } from "./cache"
 
 // This limit is fairly arbitrary, but we need to have some cap on concurrent processing.
 export const moduleResolutionConcurrencyLimit = 40
@@ -426,6 +427,12 @@ export class ModuleResolver {
       }
     })
 
+    // Make sure version is re-computed after writing files
+    if (!!resolvedConfig.generateFiles?.length) {
+      const cacheContext = pathToCacheContext(resolvedConfig.path)
+      this.garden.cache.invalidateUp(cacheContext)
+    }
+
     const module = await moduleFromConfig(this.garden, this.log, resolvedConfig, dependencies)
 
     const moduleTypeDefinitions = await this.garden.getModuleTypes()