When working with terraform across multiple target environments, it's common practice to use environment directories to organize terraform configurations that might be specific to each environment. A configuration store might have a "dev" folder containing configurations specific to the dev environment and a "prod" folder with configs specific to the production environment.

Harness terraform steps(plan and apply) support this organization when using the github config store type. In that scenario, Harness allows specification of the github repo name, and the PATH to the tf configuration files.

However, when using artifactory as the configuration store, Harness only allows specification of the Artifactory repository and the Artifact path within the repo. It does not allow specification of the CONFIGURATION path within the artifact. Instead it expects the configuration files to be in the root folder of the repository. This means a directory structure as described above will not work.