The document discusses best practices for writing a Terraform provider, including following an anatomy of provider trees, documentation trees, and example code. It advises to get inspiration from small and big providers on GitHub, and to increase confidence by adding helpers, test definitions, and releasing limited versions for feedback rather than trying to do too much initially. Developers are told to let go of their work and accept feedback in order to improve a provider.

1. OTTO JONGERIUS • DEVELOPER • ATLASSIAN • @XZU
Writing a Terraform
provider

2. @you

3. NEVER DO THIS
ANATOMY
GETTING INSPIRATION
INCREASING CONFIDENCE
Agenda
BACKGROUND
LETTING GO OF YOUR BABY

4. Background

8. Anatomy

9. Provider tree

10. Docs tree

11. Some Code

12. Example
resource

13. Never do this

14. Ignore feedback

15. Try to be too smart

16. Raise a PR as soon as
you have something

17. KISS

18. Follow contribution
guidelines

19. Getting inspiration

20. Small

21. Big

22. Increasing confidence

23. Helpers and
configs

24. Test
definitions

25. Letting go of your baby

26. Limited
exposure

27. Headcount
just bumped
to 519

28. Fancy
rendering

29. • https://tour.golang.org
• https://github.com/hashicorp/terraform
• https://www.datadoghq.com
• https://github.com/hashicorp/terraform/blob/master/.github/CONTRIBUTING.md
• https://github.com/ojongerius/terraform-provider-datadog
Links

30. Thank you!
OTTO JONGERIUS • DEVELOPER • ATLASSIAN • @XZU