feat: Procedures

[funes79]

• New resource snowflake_procedure
• As a user using Standard edition of Snowflake, had to add environment variables to prevent the creation of Materialized views and Masking policies.

Test Plan

• acceptance tests

• unit tests

References

• Implements part of Stored procedures and functions #532 and Support for snowflake_stream and snowflake_procedure #273
• https://docs.snowflake.com/en/sql-reference/sql/create-procedure.html

[alldoami]

/ok-to-test sha=6b08ca9

[github-actions]

Integration tests success for 6b08ca9

[ChrisIsidora]

@funes79 Can you take a look at the comments of @alldoami so this can be merged? I have a dependency on this feature. Thanks in advance

[ChrisIsidora]

@funes79 Can you also run the make docs so that the .md (markdown) is created? (optionally an example tf in the example folder could be nice) Thanks in advance

[funes79]

@ChrisIsidora docs and examples added.

[funes79]

@alldoami is it ok to merge?

[alldoami]

/ok-to-test sha=a736b4d

[alldoami]

If you run make docs do you get a diff?

[github-actions]

Integration tests failure for a736b4d

[ChrisIsidora]

@alldoami Added SKIP_SCIM_INTEGRATION_TESTS in #635 to fix the SCIM integration issue as it doesn't clean up properly if another test previously fails at some point or if Integrations tests are ran in parallel for different PRs.

[ChrisIsidora]

If you run make docs do you get a diff?

@alldoami I think @funes79 needs to remove the new docs for the procedure. But after merge there needs to be a new PR created after running make docs because the new docs for resources/datasources are not automatically created after commit.

[funes79]

I do not understand. On my local make docs runs fine. But I see that it failed in the Github actions. Is the any info why it causing the failure?

[funes79]

If you run make docs do you get a diff?

Yes I got a diff, so now I pushed a new commit to update the docs for procedure.

[ChrisIsidora]

I do not understand. On my local make docs runs fine. But I see that it failed in the Github actions. Is the any info why it causing the failure?

@funes79 I don't know exactly why but I had similar issues some time ago when I also introduced a new resources. I suspect that the make docs checks against the main branch and compares the docs in the PR branch and if the comparison yields a difference then it fails, but in this case for new resources it's logical that there is a difference because the resource is not there yet in the main branch. So I think the use case for the make docs check is primarily for flagging existing resources docs that needs to be updated if that resource was changed in the PR branch.

So fastest solution for now is to remove the new .md and after the merge, open a PR with only the new .md.

(Related to #632)

[alldoami]

/ok-to-test sha=40aca4d

[github-actions]

Integration tests success for 40aca4d