Where can I contribute?

[jmkacz]

In one of the issues, I was asking about helping snowflake_table move from preview to stable. The response was that it was a fairly complicated resource and you want to make sure you get the design right, so want to handle that internally. And that's totally fair.

Before I start thinking about another resource to work on, from the checklist for 1.0, I wanted to ask which ones would be good fodder for community contributions.

Could you please point me in the right direction?

[sfc-gh-jcieslak]

Hey @jmkacz 👋
Thanks for helping us out, we really appreciate it! We discussed and chose the following resources, you could start with (but if you have any other Snowflake object in mind that you would like to implement, we are open to discussions):

• application package:
  • Our internal SDK already supports it, but minor additions are needed (e.g., add missing MULTIPLE_INSTANCES and ENABLE_RELEASE_CHANNELS parameters)
  • After the SDK, you would be ready to implement the corresponding resource and data source
• session policy:
  • SDK already supports it, but also a minor change would be necessary (like adding support for ALLOWED_SECONDARY_ROLES)
  • After the SDK, you would be ready to implement the corresponding resource and data source
• notebook:
  • This one could be a bit harder and time-consuming, as there's no SDK implementation, and in Snowflake, it requires stages to be tested, which adds a bit to the difficulty (maybe could be a good follow-up to one of the simpler ones above).
  • But after implementing the SDK, as in the cases above, you could go straight into resource and data source development.
  • Additionally, we have similar objects that require stages (e.g. streams), so you could use those as guides

Let us know what you think about those object proposals, and if you would like to implement one of them. Then, I'll expand a bit on the development processes we have for both the SDK and the Terraform side.