mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #671] [MERGED] Add support for ECS metadata endpoint #1597
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1597
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/671
Author: @psyvision
Created: 11/5/2017
Status: ✅ Merged
Merged: 11/19/2017
Merged by: @ggtakec
Base:
master← Head:master📝 Commits (10+)
662f65cAdd support for ECS metadata endpoint5d54883Remove commented out codeccea87cAdded check for is_ecs during get_access_keys366f070ECS credentials bug fixes8660abaUse jsoncpp to parse AWS JSON065516cAdd jsoncpp to tavis config395f736Lower jsoncpp requirement1cbe9fbGotta pass that cppcheckgit add .5df94d7Add debug messagesa0b69d1Corrected keyval[].c_str()📊 Changes
6 files changed (+76 additions, -50 deletions)
View changed files
📝
.travis.yml(+2 -2)📝
configure.ac(+5 -5)📝
src/curl.cpp(+51 -41)📝
src/curl.h(+2 -0)📝
src/s3fs.cpp(+12 -2)📝
src/s3fs_util.cpp(+4 -0)📄 Description
This pull request resolves the issue of not using the ECS metadata endpoint when running under an ECS task role -> https://github.com/s3fs-fuse/s3fs-fuse/issues/507.
I haven't added any tests, I didn't see any that I thought were similar.
I haven't actually tested this on an ECS task yet - I will do this tomorrow!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.