Merge pull request #260 from awslabs/master

RELEASE 0.7.8

.gitignore

@@ -1,5 +1,5 @@
 # Created by https://www.gitignore.io/api/python
-
+.gitignore
 ### Python ###
 # Byte-compiled / optimized / DLL files
 rdk/__pycache__/
@@ -106,7 +106,25 @@ venv.bak/
 
 # End of https://www.gitignore.io/api/python
 
-soccer/
 
-football/
 .vscode/launch.json
+
+.vscode/settings.json
+
+myAutomationTest/
+
+myAutomationTestWithManegedRule/
+
+myAutomationTestWithManPeridoc/
+
+myAutomationTestWithResouceType/
+
+.vscode/sk.py
+
+CLOUD_TRAIL_ENCRYPTION_ENABLED/
+
+API_GW_NOT_EDGE_OPTIMISED/
+
+manageTest/
+
+football/

README.rst

@@ -1,7 +1,7 @@
 rdk
 ===
-Rule Development Kit - Version 2
-This tool should be considered in "Open Beta".  I would greatly appreciate feedback and bug reports at [email protected]/chauyu@amazon.com! You may also create an issue on this repo.
+Rule Development Kit 
+We are greatly appreciated feedback and bug reports at rdk-maintainers@amazon.com! You may also create an issue on this repo.
 
 The RDK is designed to support a "Compliance-as-Code" workflow that is intuitive and productive.  It abstracts away much of the undifferentiated heavy lifting associated with deploying AWS Config rules backed by custom lambda functions, and provides a streamlined develop-deploy-monitor iterative process.
 
@@ -241,12 +241,14 @@ email me at [email protected] if you are interested in contributing.  I'm using
 Authors
 =======
 
-* **Michael Borchert** - *Python version & current maintainer*
+* **Michael Borchert** - *Python version*
 * **Jonathan Rault** - *Design, testing, feedback*
 * **Greg Kim and Chris Gutierrez** - *Initial work and CI definitions*
 * **Henry Huang** - *Original CFN templates and other code*
-
-
+* **Ricky Chau** - *current maintainer*
+* **Santosh Kumar** - *current maintainer*
+* **Jose Obando** - *current maintainer*
+* **Sandeep Batchu** - *current maintainer*
 
 License
 =======

docs/reference/deploy.rst

@@ -17,5 +17,6 @@ Deploy
    The ``--lambda-layers`` flag can be used for attaching a comma-separated list of Lambda Layer ARNs to deploy with your Lambda function(s).
    The ``--lambda-subnets`` flag can be used for attaching a comma-separated list of Subnets to deploy your Lambda function(s).
    The ``--lambda-security-groups`` flag can be used for attaching a comma-separated list of Security Groups to deploy with your Lambda function(s).
+   The ``--custom-code-bucket`` flag can be used for providing the custom code S3 bucket name, which is not created with rdk init, for generated cloudformation template storage.
 
    Note: Behind the scenes the ``--functions-only`` flag generates a CloudFormation template and runs a "create" or "update" on the targeted AWS Account and Region.  If subsequent calls to ``deploy`` with the ``--functions-only`` flag are made with the same stack name (either the default or otherwise) but with *different Config rules targeted*, any Rules deployed in previous ``deploy``s but not included in the latest ``deploy`` will be removed.  After a functions-only ``deploy`` _only_ the Rules specifically targeted by that command (either through Rulesets or an explicit list supplied on the command line) will be deployed in the environment, all others will be removed.s

docs/reference/init.rst

@@ -23,4 +23,5 @@ Init
 
    Advanced Options:
 
-   - ``--config-bucket-exists-in-another-account``: If the bucket being used by a Config Delivery Channel exists in another account, it is possible to skip the check that the bucket exists. This is useful when using ``init`` to initialize AWS Config in an account which already has a delivery channel setup with a central bucket. Currently, the rdk lists out all the buckets within the account your are running ``init`` from, to check if the provided bucket name exists, if it doesn't then it will create it. This presents an issue when a Config Delivery Channel has been configured to push configuration recordings to a central bucket. The bucket will never be found as it doesn't exist in the same account, but cannot be created as bucket names have to be globally unique.
+   - ``--config-bucket-exists-in-another-account``: [optional] If the bucket being used by a Config Delivery Channel exists in another account, it is possible to skip the check that the bucket exists. This is useful when using ``init`` to initialize AWS Config in an account which already has a delivery channel setup with a central bucket. Currently, the rdk lists out all the buckets within the account your are running ``init`` from, to check if the provided bucket name exists, if it doesn't then it will create it. This presents an issue when a Config Delivery Channel has been configured to push configuration recordings to a central bucket. The bucket will never be found as it doesn't exist in the same account, but cannot be created as bucket names have to be globally unique.
+   - ``--skip-code-bucket-creation``: [optional] If you want to use custom code bucket for rdk, enable this and use flag ``--custom-code-bucket`` to ``rdk deploy``

rdk/__init__.py

@@ -6,4 +6,5 @@
 #
 #    or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-MY_VERSION = "0.7.7"
+MY_VERSION = "0.7.8"
+