DaShaun

Is my expectation on the right track here: - a new "Hosting type" like "k8s deployment" - deploy a "deployment.yaml" to new AKS cluster (like Dockerfile to App Service)

@findajay I haven't had time to look deeper at this myself, I had some other buildpack related issues to deal with. However, I have reached out, to see if I...

@satya108agarwal I don't think this should be an issue here. You are creating a custom config client. I looked at the example code you provided. Can you remind me why...

``` backend_config: hostname: app.terraform.io organization: dashaun token: {{environment_terraform_token}} workspaces: name: azure-dashaun-cloud ``` Same result: ``` 2019/06/28 16:39:14 terraform init command failed. Error: exit status 1 Output: Initializing modules... - module.infra...

``` 2019/06/28 21:06:23 terraform init command failed. Error: exit status 1 Output: 2019/06/28 21:06:23 [INFO] Terraform version: 0.11.14 2019/06/28 21:06:23 [INFO] Go runtime version: go1.12.4 2019/06/28 21:06:23 [INFO] CLI args:...

I've upgraded to 0.12.3 The source.env.TF_LOG: DEBUG doesn't appear to work, so the only output I get ``` ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ Terraform Apply...

I think this can be closed. At least, since version 3.0.x `spring.shell.history.enabled=false` And it no longer creates a file, so no need for the workaround.

@AbdulcelilCercenazi-TomTom did you try `spring.shell.history.enabled=false` instead of `spring.shell.command.history.enabled=false`

Just confirmed this is working as documented in the [Spring Shell Reference Docs](https://docs.spring.io/spring-shell/docs/3.1.6/docs/index.html#built-in-commands-history)

Hey! @mikrethor I found this issue while diagnosing a different bug around Ollama+Llava. The code in your example is referencing a snapshot. 1.0.0-M1 has been released since May. There are...