You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs/resources/procedure_python#snowpark_package-3
Snowflake Procedure currently requires this, but actually it is not required. Yes it needs to be passed with every request, but by default the version can be left unset. Take a look at the doc example here:
CREATE OR ALTER PROCEDURE python_add1(A NUMBER)
RETURNS NUMBER
LANGUAGE PYTHON
HANDLER='main'
RUNTIME_VERSION=3.10EXTERNAL_ACCESS_INTEGRATIONS=(example_integration)
PACKAGES=('snowflake-snowpark-python')
EXECUTE AS OWNER
AS
$$
def main(session, a):
return a+1
$$;
i would also recommend adding some examples with snowpark package to the documentation for this resource.
Category
category:resource
Object type(s)
No response
Expected Behavior
N/A
Actual Behavior
N/A
Steps to Reproduce
N/A
How much impact is this issue causing?
Low
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Hey @sfc-gh-swinkler 👋
We had some issues with this implicit package (e.g., here), so we decided to take the safe approach of specifying the Snowpark version explicitly. We are planning to revisit it later and try to make the resource guess that the passed version is specified as latest. I think there were other issues than just not knowing the current Snowpark version, but I don't remember atm (we'll do a small research before the implementation part anyway).
Terraform CLI Version
No response
Terraform Provider Version
No response
Company Name
No response
Terraform Configuration
Category
category:resource
Object type(s)
No response
Expected Behavior
N/A
Actual Behavior
N/A
Steps to Reproduce
N/A
How much impact is this issue causing?
Low
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: