v0.1.0

feat: support inline asset in `deno_deployment` & rework on `deno_ass…

…ets` (#28)

This commit adds support for inlined assets in the `deno_deployment` resource. This also involves some rework on the `deno_assets` data source, which breaks both input and output types.

Resolves #16

v0.0.4

Rename some resources and attributes (#9)

v0.0.3

fix: make @denoland/terraform-maintainers CODEOWNERS (#8)

v0.0.2

feat: generate random project name when not explicitly specified in c…

…onfig (#5)

* feat: generate random project name when not explicitly specified in config and update doc accordingly

The following three variations now work:
```
// name is not specified
resource "deno_project" "sample_project" {}

// name is specified
resource "deno_project" "sample_project2" {
  name = "sample-verification-2"
}

// name is null
resource "deno_project" "sample_project3" {
  name = null
}
```

The terraform plan will show the name when supplied by the user:
```
  # deno_project.sample_project will be created
  + resource "deno_project" "sample_project" {
      + created_at = (known after apply)
      + id         = (known after apply)
      + name       = (known after apply)
      + updated_at = (known after apply)
    }

  # deno_project.sample_project2 will be created
  + resource "deno_project" "sample_project2" {
      + created_at = (known after apply)
      + id         = (known after apply)
      + name       = "myproject"
      + updated_at = (known after apply)
    }
```

v0.0.1

fix: Update some doc strings and the readme (#4)

* feat: Rename the provider module to terraform-provider-deno.

Make the provider name match the (desired) repository name.
Update examples to work with the new provider name.

* fix: Update doc strings needed to run examples

Set the docstings for host, deno_token, and deno_deploy_organization_id.
The docstrings for the API resources still need to be written (copied
from the API documentation.)

* fix: Add a brief README.md