vercel · dglsparsons · Apr 15, 2024 · Apr 15, 2024
@@ -20,7 +20,7 @@ For more detailed information, please see the [Vercel documentation](https://ver
 
 ```terraform
 # Environment variables can be identified by their ID, or by their key and target.
-# The ID is hard to find, but can be taken from the network tab, inside developer tools, on the shared environment variable page.
+# The ID can be taken from the network tab inside developer tools, while you are on the project page.
 data "vercel_shared_environment_variable" "example" {
   id = "xxxxxxxxxxxxxxx"
 }

@@ -139,11 +139,13 @@ Import is supported using the following syntax:
 ```shell
 # If importing into a personal account, or with a team configured on
 # the provider, simply use the record id.
-# - record_id is hard to find, but can be taken from the network tab, inside developer tools, on the domains page.
+# - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
+# or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
 terraform import vercel_dns_record.example rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 # Alternatively, you can import via the team_id and record_id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
-# - record_id is hard to find, but can be taken from the network tab, inside developer tools, on the domains page.
+# - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
+# or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
 terraform import vercel_dns_record.example team_xxxxxxxxxxxxxxxxxxxxxxxx/rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 ```
@@ -91,7 +91,8 @@ Import is supported using the following syntax:
 # If importing into a personal account, or with a team configured on
 # the provider, simply use the project_id and environment variable id.
 # - project_id can be found in the project `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the project page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page,
+# or can be queried from Vercel API directly (https://vercel.com/docs/rest-api/endpoints/projects#retrieve-the-environment-variables-of-a-project-by-id-or-name)
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_project_environment_variable.example prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/FdT2e1E5Of6Cihmt
@@ -100,7 +101,8 @@ terraform import vercel_project_environment_variable.example prj_xxxxxxxxxxxxxxx
 # environment variable id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
 # - project_id can be found in the project `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the project page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page,
+# or can be queried from Vercel API directly (https://vercel.com/docs/rest-api/endpoints/projects#retrieve-the-environment-variables-of-a-project-by-id-or-name)
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_project_environment_variable.example team_xxxxxxxxxxxxxxxxxxxxxxxx/prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/FdT2e1E5Of6Cihmt

@@ -66,7 +66,7 @@ Import is supported using the following syntax:
 ```shell
 # You can import via the team_id and environment variable id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the shared environment variable page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page.
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_shared_environment_variable.example team_xxxxxxxxxxxxxxxxxxxxxxxx/env_yyyyyyyyyyyyy

@@ -1,5 +1,5 @@
 # Environment variables can be identified by their ID, or by their key and target.
-# The ID is hard to find, but can be taken from the network tab, inside developer tools, on the shared environment variable page.
+# The ID can be taken from the network tab inside developer tools, while you are on the project page.
 data "vercel_shared_environment_variable" "example" {
   id = "xxxxxxxxxxxxxxx"
 }

@@ -1,10 +1,12 @@
 # If importing into a personal account, or with a team configured on
 # the provider, simply use the record id.
-# - record_id is hard to find, but can be taken from the network tab, inside developer tools, on the domains page.
+# - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
+# or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
 terraform import vercel_dns_record.example rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 # Alternatively, you can import via the team_id and record_id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
-# - record_id is hard to find, but can be taken from the network tab, inside developer tools, on the domains page.
+# - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
+# or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
 terraform import vercel_dns_record.example team_xxxxxxxxxxxxxxxxxxxxxxxx/rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
@@ -1,7 +1,8 @@
 # If importing into a personal account, or with a team configured on
 # the provider, simply use the project_id and environment variable id.
 # - project_id can be found in the project `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the project page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page,
+# or can be queried from Vercel API directly (https://vercel.com/docs/rest-api/endpoints/projects#retrieve-the-environment-variables-of-a-project-by-id-or-name)
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_project_environment_variable.example prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/FdT2e1E5Of6Cihmt
@@ -10,7 +11,8 @@ terraform import vercel_project_environment_variable.example prj_xxxxxxxxxxxxxxx
 # environment variable id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
 # - project_id can be found in the project `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the project page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page,
+# or can be queried from Vercel API directly (https://vercel.com/docs/rest-api/endpoints/projects#retrieve-the-environment-variables-of-a-project-by-id-or-name)
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_project_environment_variable.example team_xxxxxxxxxxxxxxxxxxxxxxxx/prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/FdT2e1E5Of6Cihmt
@@ -1,6 +1,6 @@
 # You can import via the team_id and environment variable id.
 # - team_id can be found in the team `settings` tab in the Vercel UI.
-# - environment variable id is hard to find, but can be taken from the network tab, inside developer tools, on the shared environment variable page.
+# - environment variable id can be taken from the network tab inside developer tools, while you are on the project page.
 #
 # Note also, that the value field for sensitive environment variables will be imported as `null`.
 terraform import vercel_shared_environment_variable.example team_xxxxxxxxxxxxxxxxxxxxxxxx/env_yyyyyyyyyyyyy