snowflake_procedure is not idempotent

[jrobison-sb]

Provider Version

$ terraform version
Terraform v1.6.1
on darwin_arm64
+ provider registry.terraform.io/snowflake-labs/snowflake v0.73.0

Terraform Version

$ terraform version
Terraform v1.6.1
on darwin_arm64
+ provider registry.terraform.io/snowflake-labs/snowflake v0.73.0

Describe the bug

snowflake_procedure's are not idempotent.

Expected behavior

snowflake_procedure's are idempotent.

Code samples and commands

1. Create a procedure resource like this one and do terraform apply:

resource "snowflake_procedure" "dev2837" {
  name     = "DEV2837"
  language = "JAVASCRIPT"
  database = snowflake_database.default.name
  schema   = snowflake_schema.share_config[0].name
  arguments {
    name = "VIEWNAME"
    type = "VARCHAR"
  }
  return_type = "VARCHAR"
  execute_as  = "OWNER"
  statement   = <<EOT
    const dbName = '${snowflake_database.default.name}';
EOT
}

2. Go to the Snowflake console and drop the procedure, out-of-band from Terraform:

DROP PROCEDURE DEV2837(VARCHAR);

3. Run terraform apply again. Terraform should detect that the procedure no longer exists and it should offer to recreate the procedure for you. But instead, Terraform just errors out:

│ Error: 002003 (02000): SQL compilation error:
│ Procedure 'MY_DB.MY_SCHEMA.DEV2837' does not exist or not authorized.
│ 
│   with module.sandbox4_application.snowflake_procedure.dev2837,
│   on ../../modules/aws/application/snowflake.tf line 1411, in resource "snowflake_procedure" "dev2837":
│ 1411: resource "snowflake_procedure" "dev2837" {

Additional context

The behavior noticed here is essentially the same thing as described for snowflake_schema's here: #845, though I don't know if both are caused by the same code paths or not.

[sfc-gh-asawicki]

Hey @jrobison-sb.

In v0.100.0, we introduced new procedure resources. They have this behavior fixed. Please verify it and let us know.