the-distro/infra
9
0
Fork 5
Code Issues 40 Pull requests 6 Packages Projects 1 Releases Wiki Activity

feat(dns): migrate functions from gandi to dnsimple #113

Merged
janik merged 1 commit from janik/dnsimple into main 2024-09-24 18:37:58 +00:00
Conversation 3 Commits 1 Files changed 1 +42
janik commented 2024-09-23 22:28:47 +00:00
Owner
Copy link

nix run .#tf plan

...

OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

OpenTofu will perform the following actions:

  # dnsimple_zone_record.flowery_systems_CNAME_ will be created
  + resource "dnsimple_zone_record" "flowery_systems_CNAME_" {
      + id               = (known after apply)
      + name_normalized  = (known after apply)
      + priority         = (known after apply)
      + qualified_name   = (known after apply)
      + ttl              = 300
      + type             = "CNAME"
      + value            = "news.forkos.org"
      + value_normalized = (known after apply)
      + zone_id          = (known after apply)
      + zone_name        = "flowery.systems"
    }

Plan: 1 to add, 0 to change, 0 to destroy.
`nix run .#tf plan` ```plain ... OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create OpenTofu will perform the following actions: # dnsimple_zone_record.flowery_systems_CNAME_ will be created + resource "dnsimple_zone_record" "flowery_systems_CNAME_" { + id = (known after apply) + name_normalized = (known after apply) + priority = (known after apply) + qualified_name = (known after apply) + ttl = 300 + type = "CNAME" + value = "news.forkos.org" + value_normalized = (known after apply) + zone_id = (known after apply) + zone_name = "flowery.systems" } Plan: 1 to add, 0 to change, 0 to destroy. ```
janik added 1 commit 2024-09-23 22:28:51 +00:00
janik requested review from amaxine 2024-09-23 22:29:17 +00:00
amaxine approved these changes 2024-09-24 18:35:57 +00:00
amaxine left a comment
Member
Copy link

Looks good

Looks good
janik merged commit d780f18534 into main 2024-09-24 18:37:58 +00:00
janik commented 2024-09-24 18:40:30 +00:00
Author
Owner
Copy link
OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

OpenTofu will perform the following actions:

  # dnsimple_zone_record.flowery_systems_CNAME_ will be created
  + resource "dnsimple_zone_record" "flowery_systems_CNAME_" {
      + id               = (known after apply)
      + name_normalized  = (known after apply)
      + priority         = (known after apply)
      + qualified_name   = (known after apply)
      + ttl              = 300
      + type             = "CNAME"
      + value            = "news.forkos.org"
      + value_normalized = (known after apply)
      + zone_id          = (known after apply)
      + zone_name        = "flowery.systems"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  OpenTofu will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

dnsimple_zone_record.flowery_systems_CNAME_: Creating...
╷
│ Error: API returned a Validation Error for: name
│
│   with dnsimple_zone_record.flowery_systems_CNAME_,
│   on config.tf.json line 40, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]:
│   40:           "name": "",
│
│ can't be blank. Consider using an ALIAS instead.
╵
╷
│ Error: API returned an error
│
│   with dnsimple_zone_record.flowery_systems_CNAME_,
│   on config.tf.json line 45, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]:
│   45:         }
│
│ Validation failed
╵
╷
│ Error: API returned a Validation Error for: base
│
│   with dnsimple_zone_record.flowery_systems_CNAME_,
│   on config.tf.json line 45, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]:
│   45:         }
│
│ NS record (id=58753487) already exists on flowery.systems. CNAME and NS records cannot both exist on the same name., NS record (id=58753488) already exists on flowery.systems. CNAME and NS records
│ cannot both exist on the same name., NS record (id=58753489) already exists on flowery.systems. CNAME and NS records cannot both exist on the same name., NS record (id=58753490) already exists on
│ flowery.systems. CNAME and NS records cannot both exist on the same name., SOA record (id=58753486) already exists on flowery.systems. CNAME and SOA records cannot both exist on the same name.

rip 💀

``` OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create OpenTofu will perform the following actions: # dnsimple_zone_record.flowery_systems_CNAME_ will be created + resource "dnsimple_zone_record" "flowery_systems_CNAME_" { + id = (known after apply) + name_normalized = (known after apply) + priority = (known after apply) + qualified_name = (known after apply) + ttl = 300 + type = "CNAME" + value = "news.forkos.org" + value_normalized = (known after apply) + zone_id = (known after apply) + zone_name = "flowery.systems" } Plan: 1 to add, 0 to change, 0 to destroy. Do you want to perform these actions? OpenTofu will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes dnsimple_zone_record.flowery_systems_CNAME_: Creating... ╷ │ Error: API returned a Validation Error for: name │ │ with dnsimple_zone_record.flowery_systems_CNAME_, │ on config.tf.json line 40, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]: │ 40: "name": "", │ │ can't be blank. Consider using an ALIAS instead. ╵ ╷ │ Error: API returned an error │ │ with dnsimple_zone_record.flowery_systems_CNAME_, │ on config.tf.json line 45, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]: │ 45: } │ │ Validation failed ╵ ╷ │ Error: API returned a Validation Error for: base │ │ with dnsimple_zone_record.flowery_systems_CNAME_, │ on config.tf.json line 45, in resource.dnsimple_zone_record.flowery_systems_CNAME_[0]: │ 45: } │ │ NS record (id=58753487) already exists on flowery.systems. CNAME and NS records cannot both exist on the same name., NS record (id=58753488) already exists on flowery.systems. CNAME and NS records │ cannot both exist on the same name., NS record (id=58753489) already exists on flowery.systems. CNAME and NS records cannot both exist on the same name., NS record (id=58753490) already exists on │ flowery.systems. CNAME and NS records cannot both exist on the same name., SOA record (id=58753486) already exists on flowery.systems. CNAME and SOA records cannot both exist on the same name. ``` rip 💀
janik commented 2024-09-24 18:44:34 +00:00
Author
Owner
Copy link

I'm uncertain why it fails with the empty name, the code matches the example: https://registry.terraform.io/providers/dnsimple/dnsimple/latest/docs/resources/zone_record#example-usage

I'm uncertain why it fails with the empty name, the code matches the example: https://registry.terraform.io/providers/dnsimple/dnsimple/latest/docs/resources/zone_record#example-usage
amaxine commented 2024-09-24 18:44:51 +00:00
Member
Copy link

Doh, I feel stupid for not catching that you're creating a root CNAME. Those are not allowed.

Doh, I feel stupid for not catching that you're creating a root CNAME. Those are not allowed.
janik deleted branch janik/dnsimple 2024-09-24 18:53:21 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
amaxine
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: the-distro/infra#113
No description provided.
Delete branch "janik/dnsimple"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?