Skip to content

Commit

Permalink
Merge pull request #31 from equinix/checking-June2024
Browse files Browse the repository at this point in the history
chore: update the module for June 2024 current TF Provider and upstream module behaviors
  • Loading branch information
displague authored Jun 13, 2024
2 parents e85e005 + 89bac9f commit 867df0f
Show file tree
Hide file tree
Showing 17 changed files with 218 additions and 288 deletions.
2 changes: 1 addition & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
.terraform
.terraform*
!.terraform.lock.hcl
.terraform.lock.hcl
ignition.bu
terraform.tfstate
terraform.tfstate.backup
Expand Down
190 changes: 0 additions & 190 deletions .terraform.lock.hcl

This file was deleted.

18 changes: 4 additions & 14 deletions CLOUDFLARE.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This deployment automation uses the Cloudflare Managed DNS service.
This domain name (in its "base domain" form) will be used later as a value for the `cluster_basedomain` variable in the Terraform configuration.

```console
Example of the cluster_basedomain value: "domain.com"
Example of the cluster_basedomain value: "example.com"
```

1. Create Cloudflare account
Expand All @@ -32,22 +32,12 @@ This deployment automation uses the Cloudflare Managed DNS service.

1. Copy the API key

On the same page as above click on the “Get your API token” link.
Follow the directions on <https://developers.cloudflare.com/fundamentals/api/get-started/create-token/> to create an API Token for use with this zone.

You will be presented with the “API Token” tab from the “My Profile” page, click the “View” button at the “Global API key”.

Save this key value, it will be used later as value of the `dns_options` `api_key` option in the Terraform configuration.

```console
Example of the cf_api_key parameter value: "65ca543659011ba2a13b2ab06dab12c158bcb"
```

1. Copy email address

On the page above, change to the “Communication” page and save the “Email Address” value, it will be used later as the `dns_options` `email` option in the Terraform configuration.
Save this key value. You will use it in your Terraform environment by defining it as `CLOUDFLARE_API_TOKEN` in the environment.

```console
Example of the cf_email parameter value: "[email protected]"
Example of the cf_api_token parameter value: "65ca543659011ba2a13b2ab06dab12c158bcb"
```

[Top](README.md)
16 changes: 9 additions & 7 deletions EQUINIX.md
Original file line number Diff line number Diff line change
@@ -1,29 +1,31 @@
# Equinix Metal

1. Sign up for a Equinix Metal account at https://console.equinix.com/signup
1. Sign up for a Equinix Metal account at <https://console.equinix.com/signup>

2. Follow the wizard **"Getting Started with Equinix Metal"** at https://console.equinix.com/getting-started/overview that guides you through creating a project.
2. Follow the wizard **"Getting Started with Equinix Metal"** at<https://deploy.equinix.com/developers/docs/metal/getting-started/> that guides you through creating a project.

**IMPORTANT:**

Using the Equinix Metal [web portal](https://console.equinix.com/), upload one or more SSH keys to either your *"Personal Settings"* (personal SSH keys) or the newly created projects' *"Project Settings"* (project-level SSH keys).

These keys will be automatically added (to `.ssh/authorized_keys`) on every server created by you on Equinix Metal. These keys must be generated for every SSH client you will be using to access these servers.

See details at https://metal.equinix.com/developers/docs/servers/key-features/ssh-keys/
See details at <https://deploy.equinix.com/developers/docs/metal/identity-access-management/ssh-keys>

One of these SSH keys must be generated in the host system used for driving the deployment. Copy location and names of these SSH key files on that system, they will be used later as values for `ssh_private_key_path` and `ssh_public_key_path` variables in the Terraform configuration.

3. After the project has been created, navigate to its *"Project Settings"*, and at the *"General"* tab locate the project ID, copy it as is, it will be used later as a value for the `project_id` variable in the Terraform configuration.
3. After the project has been created, navigate to its *"Project Settings"*, and at the *"General"* tab locate the project ID, copy it as is, it will be used later as a value for the `metal_project_id` variable in the Terraform configuration.

```
Example of the project_id value: "e36a901f-d5e1-28e1-0f21-efb1c3676d89"
Example of the metal_project_id value: "e36a901f-d5e1-28e1-0f21-efb1c3676d89"
```

4. Create a single API key, either from either your *"Personal Settings"* or from your project *"Project Settings"*, give it a descriptive name and *"Read/Write"* permissions. Copy this key's token value as is, it will be used later as a value for the `auth_token` variable in the Terraform configuration.
4. Create a single API key, either from either your *"Personal Settings"* or from your project *"Project Settings"*, give it a descriptive name and *"Read/Write"* permissions. Copy this key's token value as is, it will be used later as a value for the `metal_auth_token` variable in the Terraform configuration.

See details at <https://deploy.equinix.com/developers/docs/metal/identity-access-management/api-keys/>

```
Example of the auth_token value: "atBncno1a8ipxEYAKNTpuFp7CyyDDZVA"
Example of the metal_auth_token value: "atBncno1a8ipxEYAKNTpuFp7CyyDDZVA"
```

Next, follow [this](CLOUDFLARE.md)
Expand Down
8 changes: 0 additions & 8 deletions OWNERS.md

This file was deleted.

Loading

0 comments on commit 867df0f

Please sign in to comment.