Repository navigation
Debug output #16
Description
When running @ocobleseqx's fantastic K8s provider code, I see the following DEBUG output. I believe it originates from the TF provider. I've asked our engineering team on how to suppress it. (I've seen other Pulumi providers that have the same issue.)
Diagnostics:
pulumi:pulumi:Stack (equinix-ts-metal-k8s-cluster-dev):
2023/06/20 12:25:30 [DEBUG] POST https://api.equinix.com/metal/v1/projects
2023/06/20 12:25:35 [DEBUG] POST https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/bgp-configs
2023/06/20 12:25:35 [DEBUG] GET https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485
2023/06/20 12:25:35 [DEBUG] GET https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/bgp-config
2023/06/20 12:25:39 [DEBUG] POST https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/ips
2023/06/20 12:25:40 [DEBUG] POST https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/api-keys
2023/06/20 12:25:40 [DEBUG] GET https://api.equinix.com/metal/v1/ips/7afbe1c3-a11a-47fa-a8e6-1e92210937e7
2023/06/20 12:25:40 [DEBUG] GET https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/api-keys?include=project
2023/06/20 12:25:40 [DEBUG] POST https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/ssh-keys
2023/06/20 12:25:40 [DEBUG] GET https://api.equinix.com/metal/v1/ips/7afbe1c3-a11a-47fa-a8e6-1e92210937e7?include=facility%2Cmetro%2Cproject%2Cvrf&types=public_ipv4%2Cglobal_ipv4%2Cprivate_ipv4%2Cpublic_ipv6%2Cvrf
2023/06/20 12:25:40 [DEBUG] GET https://api.equinix.com/metal/v1/ssh-keys/dccefd46-8afe-4ba2-be66-415e22a2e040
2023/06/20 12:25:45 [DEBUG] POST https://api.equinix.com/metal/v1/projects/b82a4681-0e13-4bdc-b81a-84614a0b6485/devices
2023/06/20 12:25:56 [DEBUG] GET https://api.equinix.com/metal/v1/devices/00c782ba-d5d6-4184-8e3b-4278bc2cb33c?include=project%2Cfacility
Activity