upload-configuration action on GitHub Enterprise

Hi,

I am using the actions on GitHub Enterprise and seeing some issues while using upload-configuration action.

I can see the list the files are under config_directory in my actions in previous step and when I use upload-configuration as below, I am getting the error message "error uploading configuration version to Terraform Cloud: failed to find files under the path "/github/workspace/terraform/apim/ash/dev": stat /github/workspace/terraform/apim/ash/dev: no such file or directory".

If I put the configuration files under root of the repo, upload configuration works okay but this time not passing the output "configuration_version_id" to the next step.

Is there a way to use these actions easily with GitHub Enterprise and Terraform Enterprise ?

Thanks

Jon

`/usr/bin/docker run --name jontfciv130_8693a0 --label c3f261 --workdir /github/workspace --rm -e "HTTP_PROXY" -e "http_proxy" -e "HTTPS_PROXY" -e "https_proxy" -e "TF_CLOUD_ORGANIZATION" -e "TF_API_TOKEN" -e "TF_HOSTNAME" -e "TF_WORKSPACE" -e "CONFIG_DIRECTORY" -e "INPUT_WORKSPACE" -e "INPUT_DIRECTORY" -e "INPUT_SPECULATIVE" -e "INPUT_HOSTNAME" -e "INPUT_TOKEN" -e "INPUT_ORGANIZATION" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/actions-runner/_work/_temp/_github_home":"/github/home" -v "/actions-runner/_work/_temp/_github_workflow":"/github/workflow" -v "/actions-runner/_work/_temp/_runner_file_commands":"/github/file_commands" -v "/actions-runner/_work/iac_configs_apim/iac_configs_apim":"/github/workspace" hashicorp/tfci:v1.3.0 "tfci" "-hostname=" "-token=" "-organization=" "upload" "-workspace=tf_ash_apim_dev" "-directory=./terraform/apim/ash/dev" "-speculative=true"`

Beginne damit, die upload-configuration action mit dem gemeldeten Wert `config_directory` und dem Docker-Aufruf mit `hashicorp/tfci:v1.3.0` zu reproduzieren. Vergleiche das Verhalten für Dateien unter `./terraform/apim/ash/dev` mit Dateien im Repository-Stammverzeichnis und überprüfe, ob die Ausgabe `configuration_version_id` den folgenden Schritt erreicht.

Vom Indexierungsmodell aus dem Issue-Text verfasst.