From c0916d271f1b31af2a145ca2d4fb1d00bb431d4b Mon Sep 17 00:00:00 2001 From: Anna Lushnikova Date: Thu, 20 Feb 2025 14:42:00 -0500 Subject: [PATCH 1/3] update contributing with notes about generating release notes when publish the release --- CONTRIBUTING.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 378ada184..8dc97959c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -197,15 +197,19 @@ The dedicated DigitalOcean team is responsible for releasing the provider. git push "$origin" tag "$new_version" ``` -This repository contains a GitHub Action configured to automatically build and +         This repository contains a GitHub Action configured to automatically build and publish assets for release when a tag is pushed that matches the pattern `v*` (ie. `v0.1.0`). -A [Goreleaser](https://goreleaser.com/) configuration is provided that produces +         A [Goreleaser](https://goreleaser.com/) configuration is provided that produces build artifacts matching the [layout required](https://www.terraform.io/docs/registry/providers/publishing.html#manually-preparing-a-release) to publish the provider in the Terraform Registry. -Releases will appear as drafts. Once marked as published on the GitHub Releases page, +6. Publish the release. +A new release will appear as drafts. +Hit "Generate Release Notes" when publish the release. +Mark the release as Latest. +Once marked as published on the GitHub Releases page, they will become available via the Terraform Registry. Reviewing Pull Requests From da119aebd61f90fbdc3f5d22db5eb1de63f4709f Mon Sep 17 00:00:00 2001 From: Anna Lushnikova Date: Fri, 21 Feb 2025 11:29:38 -0500 Subject: [PATCH 2/3] update contributing with notes about generating release notes when publish the release (#1328) --- CONTRIBUTING.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 378ada184..8dc97959c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -197,15 +197,19 @@ The dedicated DigitalOcean team is responsible for releasing the provider. git push "$origin" tag "$new_version" ``` -This repository contains a GitHub Action configured to automatically build and +         This repository contains a GitHub Action configured to automatically build and publish assets for release when a tag is pushed that matches the pattern `v*` (ie. `v0.1.0`). -A [Goreleaser](https://goreleaser.com/) configuration is provided that produces +         A [Goreleaser](https://goreleaser.com/) configuration is provided that produces build artifacts matching the [layout required](https://www.terraform.io/docs/registry/providers/publishing.html#manually-preparing-a-release) to publish the provider in the Terraform Registry. -Releases will appear as drafts. Once marked as published on the GitHub Releases page, +6. Publish the release. +A new release will appear as drafts. +Hit "Generate Release Notes" when publish the release. +Mark the release as Latest. +Once marked as published on the GitHub Releases page, they will become available via the Terraform Registry. Reviewing Pull Requests From f5763d1232811eda679c1ed9ca9d4c80a6d2110a Mon Sep 17 00:00:00 2001 From: Ashwani Date: Wed, 26 Feb 2025 19:27:12 +0530 Subject: [PATCH 3/3] Added documentation for reserved ipv6 (#1330) * added documentation for reserved ipv6 * fixed fmt issues --- docs/data-sources/reserved_ipv6.md | 41 ++++++++++++++++++ docs/resources/reserved_ipv6.md | 35 +++++++++++++++ docs/resources/reserved_ipv6_assignment.md | 50 ++++++++++++++++++++++ 3 files changed, 126 insertions(+) create mode 100644 docs/data-sources/reserved_ipv6.md create mode 100644 docs/resources/reserved_ipv6.md create mode 100644 docs/resources/reserved_ipv6_assignment.md diff --git a/docs/data-sources/reserved_ipv6.md b/docs/data-sources/reserved_ipv6.md new file mode 100644 index 000000000..93c51b318 --- /dev/null +++ b/docs/data-sources/reserved_ipv6.md @@ -0,0 +1,41 @@ +--- +page_title: "DigitalOcean: digitalocean_reserved_ipv6" +subcategory: "Networking" +--- + +# digitalocean_reserved_ipv6 + +Get information on a reserved IPv6. This data source provides the region_slug and droplet id as configured on your DigitalOcean account. This is useful if the reserved IPv6 in question is not managed by Terraform or you need to find the Droplet the IP is +attached to. + +An error is triggered if the provided reserved IPv6 does not exist. + +## Example Usage + +Get the reserved IPv6: + +```hcl + +resource "digitalocean_reserved_ipv6" "foo" { + region_slug = "nyc3" +} + +data "digitalocean_reserved_ipv6" "foobar" { + ip = digitalocean_reserved_ipv6.foo.ip +} + +``` + +## Argument Reference + +The following arguments are supported: + +* `ip` - (Required) The allocated IPv6 address of the specific reserved IPv6 to retrieve. + +## Attributes Reference + +The following attributes are exported: + +* `region_slug`: The region that the reserved IPv6 is reserved to. +* `urn`: The uniform resource name of the reserved IPv6. +* `droplet_id`: The Droplet id that the reserved IP has been assigned to. diff --git a/docs/resources/reserved_ipv6.md b/docs/resources/reserved_ipv6.md new file mode 100644 index 000000000..99dbb4a01 --- /dev/null +++ b/docs/resources/reserved_ipv6.md @@ -0,0 +1,35 @@ +--- +page_title: "DigitalOcean: digitalocean_reserved_ipv6" +subcategory: "Networking" +--- + +# digitalocean\_reserved_ipv6 + +Provides a DigitalOcean reserved IPv6 to represent a publicly-accessible static IPv6 addresses that can be mapped to one of your Droplets. + +~> **NOTE:** Reserved IPv6s can be assigned to a Droplet using +`digitalocean_reserved_ipv6_assignment` resource only. + +## Example Usage + +```hcl +resource "digitalocean_reserved_ipv6" "foobar" { + region_slug = "nyc3" +} +``` + +## Argument Reference + +The following arguments are supported: + +* `region_slug` - (Required) The region that the reserved IPv6 needs to be reserved to. + + +## Import + +Reserved IPv6s can be imported using the `ip`, e.g. + +``` +terraform import digitalocean_reserved_ipv6.myip +2409:40d0:fa:27dd:9b24:7074:7b85:eee6 +``` diff --git a/docs/resources/reserved_ipv6_assignment.md b/docs/resources/reserved_ipv6_assignment.md new file mode 100644 index 000000000..2c936710f --- /dev/null +++ b/docs/resources/reserved_ipv6_assignment.md @@ -0,0 +1,50 @@ +--- +page_title: "DigitalOcean: digitalocean_reserved_ipv6_assignment" +subcategory: "Networking" +--- + +# digitalocean\_reserved_ipv6_assignment + +Provides a resource for assigning an existing DigitalOcean reserved IPv6 to a Droplet. This +makes it easy to provision reserved IPv6 addresses that are not tied to the lifecycle of your Droplet. + +## Example Usage + +```hcl +resource "digitalocean_reserved_ipv6" "foobar" { + region_slug = "nyc3" +} + +resource "digitalocean_droplet" "foobar" { + image = "ubuntu-22-04-x64" + name = "tf-acc-test-01" + region = "nyc3" + size = "s-1vcpu-1gb" + ipv6 = true +} + +resource "digitalocean_reserved_ipv6_assignment" "foobar" { + ip = digitalocean_reserved_ipv6.foobar.ip + droplet_id = digitalocean_droplet.foobar.id + + lifecycle { + create_before_destroy = true + } +} +``` + +## Argument Reference + +The following arguments are supported: + +* `ip` - (Required) The reserved IPv6 to assign to the Droplet. +* `droplet_id` - (Required) The ID of Droplet that the reserved IPv6 will be assigned to. + +## Import + +Reserved IPv6 assignments can be imported using the reserved IPv6 itself and the `id` of +the Droplet joined with a comma. For example: + +``` +terraform import digitalocean_reserved_ipv6_assignment.foobar 2409:40d0:fa:27dd:9b24:7074:7b85:eee6,123456 +```