Run bundle summary with --force-pull (#1181)

Fixes a problem with projects that use older version of the databricks
provider (than the one with ship the extension with).

With the updated logic we always regenerating internal terraform state
when we execute `summary` command, which sets the correct provider
version for the terraform

Author: ilia-db

packages/databricks-vscode/src/bundle/models/BundleRemoteStateModel.ts

@@ -44,7 +44,6 @@ export class BundleRemoteStateModel extends BaseModelWithStateCache<BundleRemote
     public target: string | undefined;
     public authProvider: AuthProvider | undefined;
     protected mutex = new Mutex();
-    private refreshInterval: NodeJS.Timeout | undefined;
     private logger = logging.NamedLogger.getOrCreate(Loggers.Bundle);
 
     constructor(
@@ -149,8 +148,5 @@ export class BundleRemoteStateModel extends BaseModelWithStateCache<BundleRemote
 
     dispose() {
         super.dispose();
-        if (this.refreshInterval !== undefined) {
-            clearInterval(this.refreshInterval);
-        }
     }
 }

packages/databricks-vscode/src/cli/CliWrapper.ts

@@ -334,7 +334,17 @@ export class CliWrapper {
         configfilePath?: string,
         logger?: logging.NamedLogger
     ) {
-        const cmd = [this.cliPath, "bundle", "summary", "--target", target];
+        const cmd = [
+            this.cliPath,
+            "bundle",
+            "summary",
+            "--target",
+            target,
+            // Forces the CLI to regenerate local terraform state and pull the remote state.
+            // Regenerating terraform state is useful when we want to ensure that the provider version
+            // used in the local state matches the bundled version we supply with the extension.
+            "--force-pull",
+        ];
 
         logger?.info(
             `Refreshing bundle configuration for target ${target}...`,