Coder Social home page Coder Social logo

Comments (5)

alexott avatar alexott commented on August 12, 2024

@tiagoshin, can you provide sample values for all variables? Also, your TF template doesn't have any value for workload_type, workload_size, etc.

from terraform-provider-databricks.

tiagoshin avatar tiagoshin commented on August 12, 2024

Sure, the variables are like:

  • var.environment = "dev"
  • var.service = "service-name"
  • var.databricks_scale_to_zero_enabled = "true"
  • var.databricks_min_provisioned_throughput = 3600
  • var.databricks_max_provisioned_throughput = 7200

Also, your TF template doesn't have any value for workload_type, workload_size, etc.

That's the point! The new Databricks model serving model is not based on workload size and type. For e.g., we cannot even define them on UI. Instead, we use min_provisioned_throughput and max_provisioned_throughput, so the hardware is assigned by Databricks.
So, if I'm not defining those values, why does Terraform want to change them?

from terraform-provider-databricks.

alexott avatar alexott commented on August 12, 2024

@tiagoshin

Can you attach logs as per first section of troubleshooting guide?

Regarding workload_type and workload_size - it looks like they are set on the backend, so they are populated in the TF state, and when apply happens, then TF figures out that they aren't set, and tries to reset them. To avoid resetting of that values they need to be correctly marked in the code as computed. Or they should be not populated by the backend...

from terraform-provider-databricks.

tiagoshin avatar tiagoshin commented on August 12, 2024

@alexott How do we mark them as computed?

from terraform-provider-databricks.

clintbxtreme avatar clintbxtreme commented on August 12, 2024

To test I also tried defining workload_type and workload_size but terraform is still wanting to change the scale_to_zero_enabled flag even tho it was previously applied initially:

  ~ resource "databricks_model_serving" "chat_model" {
        id                  = "name of the resource"
        name                = "name of the resource"
        # (1 unchanged attribute hidden)
      ~ config {
          ~ served_entities {
                name                       = "name of the resource"
              ~ scale_to_zero_enabled      = false -> true
                # (7 unchanged attributes hidden)
            }
            # (1 unchanged block hidden)
        }
    }

This also resulted in the same error as above

from terraform-provider-databricks.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.