Customers have requested that we promote our terraform provider tov1.0. The product is quite stable and, of course, is used in every one of our customers' deployments.

To show that this is no longer breaking, we should promote the release versioning tov1.X.X; before we do so, thedocs should meetv1.0 standards. As I mentioned, we don't get many stability requests, but there are often requests for elaboration on the provider's behavior. There are a few resources/data sources that are missing code examples, or may be enriched via context.

Docs checklist for v1.0

• Resource docs
  • coder_env
    • Code examples
  • coder_script
    • Code examples
    • Explanation on parallel execution
    • Startup script implications
    • Link to discussion onexecution ordering (frequently requested)
      • not necessary
• Data source docs
  • coder_external_auth
    • Code examples
    • Link to coder.com external auth docs
  • coder_parameter
    • Code examples (show validation types, monotonicity, etc)
      • Should just grep the closed customer requests oncoder_parameter (like this)
    • Code example not consumed in docs generation #242
    • Optional: Fix inline link undericon
    • Optional: Link to discussion on coder_parameter extension
  • coder_provisioner
    • Code example
    • Optional: Fix inline links
  • coder_workspace
    • Optional: Expand code examples
      • Not enough attributes to warrant further examples
  • coder_workspace_owner
    • Code examples
• Get template details in terraform coder#13122 - indicate required version of coder for resource functionality
• Improve version compatibility #224
• bump go version #222
• docs missing deprecation notice and migration steps #237
• [ ]Remove deprecated resources/data sources #250
• docs: improve docs by using code-styled markdown #260