googleapis / gcp-metadata

Get the metadata from a Google Cloud Platform environment

googleapis/gcp-metadata Issues

gcp metadata cloud functions: should access the metadata service on GCF failed
Updated a year ago3
refactor: Remove `@babel/plugin-proposal-private-methods`
Updated a year ago1
refactor: Remove `skipLibCheck` in TSConfig
Updated a year ago
Metadata queried on every request.
Updated a year ago2
Permanent redirect to from instance to instance/
Updated a year ago5
Typo in SECONDARY_HOST_ADDRESS
Closed a year ago
Code running in Cloud Build gets stuck trying to fetch metadata in v5.1.0
Closed a year ago12
refactor!: Remove `json-bigint`
Updated a year ago
Improve documentation
Closed a year ago4
gcp metadata cloud functions: should access the metadata service on GCF failed
Closed a year ago2
unit test: should fail on isAvailable if GCE_METADATA_HOST times out failed
Closed a year ago2
unit test: should fail on isAvailable if request times out failed
Closed a year ago2
gcp-residency detectGCPResidency: should return `false` !`isGoogleCloudServerless` && !`isGoogleComputeEngine` failed
Closed a year ago2
gcp metadata cloud functions: "before all" hook for "should access the metadata service on GCF" failed
Closed a year ago1
unit test: should fail on isAvailable if request times out failed
Closed 2 years ago1
unit test: should fail on isAvailable if GCE_METADATA_HOST times out failed
Closed 2 years ago1
gcp metadata cloud functions: should access the metadata service on GCF failed
Closed 2 years ago1
installation: should be able to use the d.ts failed
Closed 2 years ago2
gcp metadata cloud build: should access the metadata service on GCB failed
Closed 2 years ago
gcp metadata cloud functions: "after all" hook for "should access the metadata service on GCF" failed
Closed 2 years ago
gcp metadata cloud functions: "before all" hook for "should access the metadata service on GCF" failed
Closed 2 years ago
Your .repo-metadata.json file has a problem 🤒
Updated 2 years ago
Is it possible to remove the vulnerability introduced by json-bigint?
Closed 2 years ago5
installation: should be able to use the d.ts failed
Closed 3 years ago2
gcp metadata cloud functions: "before all" hook for "should access the metadata service on GCF" failed
Closed 3 years ago1
gcp metadata cloud build: should access the metadata service on GCB failed
Closed 3 years ago1
system test: should accept an object with property and query fields failed
Closed 3 years ago1
Dependency Dashboard
Closed 3 years ago
Warning: a recent release failed
Closed 3 years ago
gcp metadata cloud build: should access the metadata service on GCB failed
Closed 3 years ago2
Warning: a recent release failed
Closed 3 years ago
Undocumented results
Closed 4 years ago2
Action Required: Fix Renovate Configuration
Closed 3 years ago
installation: should be able to use the d.ts failed
Closed 4 years ago
Warning: a recent release failed
Closed 4 years ago
Synthesis failed for gcp-metadata
Closed 4 years ago5
Synthesis failed for gcp-metadata
Closed 4 years ago1
Intermittent ECONNREFUSED to 169.254.169.254 in GKE
Closed 4 years ago11
Synthesis failed for gcp-metadata
Closed 4 years ago1
Synthesis failed for gcp-metadata
Closed 4 years ago1
Simplify fastFailMetadataRequest() logic
Closed 4 years ago
Reconsider the error code whitelist approach in isAvailable()
Closed 4 years ago7
Mocha Tests: should throw if request options are passed failed
Closed 4 years ago3
Mocha Tests: should throw if invalid options are passed failed
Closed 4 years ago3
Mocha Tests: should return error if statusCode is not 200 failed
Closed 4 years ago2
Mocha Tests: should retry if the initial request fails failed
Closed 4 years ago3
Mocha Tests: should return error when flavor header is incorrect failed
Closed 4 years ago1
Mocha Tests: "after each" hook in "{root}" failed
Closed 4 years ago1
Mocha Tests: should return error when res is empty failed
Closed 4 years ago1
Mocha Tests: should return the request error failed
Closed 4 years ago1