Skip to content

Commit

Permalink
Preparing 1.2.0 release
Browse files Browse the repository at this point in the history
  • Loading branch information
mbrossard committed May 5, 2017
1 parent 50182a5 commit d1e0913
Show file tree
Hide file tree
Showing 5 changed files with 33 additions and 5 deletions.
14 changes: 12 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,18 @@
## 1.2.0 (2017-05-05)
- #48 and #49: Improvements for running outside of EC2 (@mbrossard):
- Set DISABLE_YUM_S3_IAM environment variable to disable IAM
authentication, to be used with S3 bucket IP white-listing.
- Set AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and optionally
AWS_SESSION_TOKEN environment variables to be used as fallback in
case IAM roles are not available
- #50: Fix for cross-region STS authentication (@jonnangle)
- #55: Fix for regression on 'us-east-1' (@mestudd, @mbrossard)

## 1.1.2 (2017-02-21)
- #53: Fix for no-region regression introduced by #51
- #53: Fix for no-region regression introduced by #51 (@mbrossard)

## 1.1.1 (2017-02-16)
- #51: Add support for cn-north-1 region
- #51: Add support for cn-north-1 region (@mbrossard)

## 1.1.0 (2016-07-11)
- #32: Add support for AWS v4 signature (@mbrossard)
Expand Down
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
NAME = yum-plugin-s3-iam
VERSION = 1.1.2
VERSION = 1.2.0
RELEASE = 1
ARCH = noarch

Expand Down
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,18 @@ There are 2 types of S3 URLs:
When using HTTP/S and a bucket name containing a dot (`.`) you need to
use the path-style URL syntax.

## Use outside of EC2

Some use-cases (Continuous Integration, Docker) involve S3-hosted yum
repositories being accessed from outside EC2. For those cases two
options are available:
- Use AWS API keys in AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY (and
optionally AWS_SESSION_TOKEN) environment variables. Those will be
used as a fallback if IAM role credentials can not be accessed.
- Defining the environment DISABLE_YUM_S3_IAM to 1 will disable the
use of the yum-s3-iam plugin. This should be used with S3 bucket IP
white-listing.

## Limitations

Currently the plugin does not support:
Expand Down
2 changes: 1 addition & 1 deletion s3iam.py
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
__email__ = "[email protected]"
__copyright__ = "Copyright 2012, Julius Seporaitis"
__license__ = "Apache 2.0"
__version__ = "1.1.2"
__version__ = "1.2.0"


__all__ = ['requires_api_version', 'plugin_type', 'CONDUIT',
Expand Down
8 changes: 7 additions & 1 deletion yum-plugin-s3-iam.spec
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,17 @@ rm -rf ${RPM_BUILD_ROOT}
/usr/lib/yum-plugins/s3iam.py*

%changelog
* Fri May 05 2017 Mathias Brossard <[email protected]> 1.2.0-1
- Improvements for running outside of EC2 (@mbrossard)
- Fix for cross-region STS authentication (@jonnangle)
- Fix for regression on 'us-east-1' (@mestudd, @mbrossard)

* Tue Feb 21 2017 Mathias Brossard <[email protected]> 1.1.2-1
- Fix for no-region regression introduced by cn-north-1 region support
(@mbrossard)

* Thu Feb 16 2017 Mathias Brossard <[email protected]> 1.1.1-1
- Add support for cn-north-1 region
- Add support for cn-north-1 region (@mbrossard)

* Wed Jul 11 2016 Mathias Brossard <[email protected]> 1.1.0-1
- Add support for AWS v4 signature (@mbrossard)
Expand Down

0 comments on commit d1e0913

Please sign in to comment.