Skip to content
This repository was archived by the owner on Jan 5, 2019. It is now read-only.

Bug 1316698 - EC2 metadata compat#84

Merged
jonasfj merged 1 commit intomasterfrom
bug-1316698
Nov 11, 2016
Merged

Bug 1316698 - EC2 metadata compat#84
jonasfj merged 1 commit intomasterfrom
bug-1316698

Conversation

@jonasfj
Copy link
Contributor

@jonasfj jonasfj commented Nov 11, 2016

// Make result compatibility with how EC2 metadata service let's instances
// access IAM roles
if (req.query.format === 'iam-role-compat') {
return res.status(200).json({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This avoids the schema validation.. clever :)

debug("### s3.putObject");
await s3.putObject({
Bucket: bucket,
Key: 'folder1/' + id,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why create a new object on every test run?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to avoid consistency issues... this uses the garbage bucket where everything expires after 24 hours.

@djmitche
Copy link
Contributor

     Error: getaddrinfo ENOTFOUND taskclusterdev.table.core.windows.net taskclusterdev.table.core.windows.net:443

why does DNS suck?

@jonasfj
Copy link
Contributor Author

jonasfj commented Nov 11, 2016

why does DNS suck?

Not a DNS issue taskclusterdev was my personal account after you leaked creds I just deleted it... So rotating tc-auth tests to use jungle account.

@jonasfj jonasfj merged commit a613065 into master Nov 11, 2016
@jonasfj jonasfj deleted the bug-1316698 branch November 11, 2016 21:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants