From 7c84f3d5b5f53f84f4bc24994931ef7a5875b81a Mon Sep 17 00:00:00 2001
From: Jose Diaz-Gonzalez <email@josediazgonzalez.com>
Date: Mon, 13 Feb 2017 18:27:55 -0500
Subject: [PATCH] Release version 0.7.0

---
 CHANGES.rst       | 50 +++++++++++++++++++++++++++++++++++++++++++++++
 docs/conf.py      |  4 ++--
 kappa/__init__.py |  2 +-
 3 files changed, 53 insertions(+), 3 deletions(-)

diff --git a/CHANGES.rst b/CHANGES.rst
index 8ee6871..6908a14 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -1,6 +1,56 @@
 Changelog
 =========
 
+0.7.0 (2017-02-13)
+------------------
+
+- Support alternate git status output. [Jose Diaz-Gonzalez]
+
+- Do not force use of profile for AWS session. [Wilfrido Vidana]
+
+   * Let boto3 handle credentials, do not force the use of profile
+
+
+- Added documentation for Environment Variables. [Bruno Carrier]
+
+- Added environment variable support. [Bruno Carrier]
+
+- Allow deploys with existing role. [Wilfrido Vidana]
+
+   * No policy needed
+   * Use role name
+
+
+- Add lambdaInvoke permissions for SNS Events. [Tim Van de Walle]
+
+  SNS events need to be given the lambdaInvoke permission so that they can
+  call the lambda function.
+
+  Fixes #76.
+
+
+- Adding fix for issue 90. Adding _get_notification_spec function to s3
+  event source. [Dylan Armstrong]
+
+- Adding fix for issue 89. [Dylan Armstrong]
+
+- Removing environment suffix from function name/arn. [Dylan Armstrong]
+
+- Adding fixes for issues 87 and 88. [Dylan Armstrong]
+
+- Adding fix for issue 85: Updating cloudwatch event source causes
+  trigger to show multiple times in AWS console. [Dylan Armstrong]
+
+- LambdaFunctionArn shouldn't be suffixed with the environment. [Igor
+  Serko]
+
+  When configuring the S3 bucket event the function `add` builds the `LambdaFunctionConfigurations` which specifies the `LambdaFunctionArn`. The ARN should be the functions *exact* ARN and not suffixed by the environment ex.`arn:aws:lambda:us-west-1:1234567890123:function:bigquery_commit:main-env`.
+
+  It makes the Lambda UI and the S3 event sources UI confused as they don't recognize that the specific Lambda function even exists.
+
+  The reason why I made this change is because I had problems applying the bucket event cross-account and could not do this without this change.
+
+
 0.6.0 (2016-08-03)
 ------------------
 
diff --git a/docs/conf.py b/docs/conf.py
index 32c91ac..f67b206 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -61,9 +61,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '0.6.0'
+version = '0.7.0'
 # The full version, including alpha/beta/rc tags.
-release = '0.6.0'
+release = '0.7.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/kappa/__init__.py b/kappa/__init__.py
index 790a50b..44f6b91 100644
--- a/kappa/__init__.py
+++ b/kappa/__init__.py
@@ -13,4 +13,4 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-__version__ = '0.6.0'
+__version__ = '0.7.0'