Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
Go to file
Michael Alphonso 04bca9e9f2 I started out on version 2016.11.0 and went to 2016.11.1 for a few things, then debugged some other things a bit further, then merged with develop. Here are my findings:
### What does this PR do?
**module: boto_rds**
* updated `boto_rds.create`'s of describe return value changes from `{'db_instance_status': string}` to `{'rds': 'DBInstanceStatus': string}` -- fixes Runtime Exception
* updated `boto_rds.get_endpoint`:
  - return the same values as in previous `boto2.rds2` implementation -- since: fae87f1d5e (diff-59e36191d3e2ecda4e684feddb25b2d0L452)
  - Added sanity check for 'Endpoint' index to avoid exception when endpoint is not available (happens during initial "backing-up" stage after creation.)
  - Returns only string endpoint (Address) with no port value. Previous rds2 implementation only returned address.
  - Rolled back a change to describe here: b5a2e11e60

> Should either roll back to what it was, or if it should include the port (return a dict instead of string??)..I'd listen to reason :)
>     i've already updated states to split port off if colon is found.. so either implementation will work for me now.. not sure of scope of impact to any others..

* updated `boto_rds.delete` to accept tags param and pass it thru to `__salt__['boto_rds.exists']` when checking if rds has been completely deleted to be consistent with other uses of the exists calls in the module

**state: boto_rds**
* updated `boto_rds.present`'s sample code-block to reflect the new syntax with tags in a dict instead of list of lists. In the latest implementation in the module, `boto_rds._tag_doc` is used to build the tag list according to the boto3 api reference: http://boto3.readthedocs.io/en/latest/reference/services/rds.html?highlight=rds#RDS.Client.create_db_instance
* fix docblocks to reflect that the tags is expected to be a 'dict'
* fixed use of `boto_rds.exists` return data to expect `{'exists': bool}` instead of `bool`
* updated `boto_rds.absent` to pass in tags to `__salt__['boto_rds.delete']` to go along with the change in the method signature in the module

### What issues does this PR fix or reference?

Rebasing #38284 (totally deleted branch by accident, lol)

Cheers 👍
2016-12-16 14:01:57 -05:00
.github clean up HACKING.rst doc 2016-11-03 16:47:59 -05:00
conf Merge branch '2016.11' into 'develop' 2016-12-07 16:31:11 -07:00
doc Merge branch '2016.11' into 'develop' 2016-12-15 20:47:35 -07:00
pkg Merge pull request #37858 from cournape/installers/osx/support-maverick 2016-11-27 12:54:05 +02:00
requirements Merge branch '2016.11' into 'develop' 2016-12-13 11:29:16 -07:00
salt I started out on version 2016.11.0 and went to 2016.11.1 for a few things, then debugged some other things a bit further, then merged with develop. Here are my findings: 2016-12-16 14:01:57 -05:00
scripts add 2.6 support 2016-07-29 10:00:28 +10:00
templates add email and name to test templates, removed typo in module_test template 2016-07-28 13:42:36 +10:00
tests Merge branch '2016.11' into 'develop' 2016-12-15 20:47:35 -07:00
.codeclimate.yml Configuration file for Code Climate static code analysis. 2015-05-05 13:49:46 -03:00
.editorconfig Added .editorconfig for easier editing. 2015-10-04 21:35:51 -04:00
.gitignore Revert "Fix integration tests launching - remove redundant "config_dir" argument in call to ShellTestCase.run_run from SaltDaemonScriptBase._wait_until_running" 2016-10-20 19:48:59 +09:00
.pylintrc update lint with new thorium builtins 2016-02-02 17:51:28 -07:00
.testing.pylintrc use the cache runner in the cache roster file to get grains 2016-11-01 09:38:34 -05:00
.travis.yml move requirements files into requirements dir 2014-12-27 17:29:03 -07:00
AUTHORS add nodegroups ext_pillar (#33179) 2016-05-13 08:26:13 -06:00
CONDUCT.md SaltStack's code of conduct 2016-09-16 00:32:01 +09:00
COPYING Update Salt's licensing information to include cptestcase 2016-09-01 18:46:13 +09:00
HACKING.rst clean up HACKING.rst doc 2016-11-03 16:47:59 -05:00
LICENSE Updated copyright to 2016 2016-01-01 01:31:48 +00:00
MANIFEST.in move requirements files into requirements dir 2014-12-27 17:29:03 -07:00
README.rst change links to develop 2016-10-21 15:38:15 -06:00
setup.py Merge branch '2016.3' into 2016_3_develop 2016-09-26 21:47:32 +09:00

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

==================
What is SaltStack?
==================

SaltStack makes software for complex systems management at scale.
SaltStack is the company that created and maintains the Salt Open
project and develops and sells SaltStack Enterprise software, services
and support. Easy enough to get running in minutes, scalable enough to
manage tens of thousands of servers, and fast enough to communicate with
them in *seconds*.

Salt is a new approach to infrastructure management built on a dynamic
communication bus. Salt can be used for data-driven orchestration,
remote execution for any infrastructure, configuration management for
any app stack, and much more.

Download Salt Open
==================

Salt Open is tested and packaged to run on CentOS, Debian, RHEL, Ubuntu,
Windows. Download Salt Open and get started now.

`<https://repo.saltstack.com/>`_

`Installation Instructions <https://docs.saltstack.com/en/latest/topics/installation/index.html>`_

SaltStack Documentation
=======================

Installation instructions, getting started guides, and in-depth API
documentation.

`<https://docs.saltstack.com/en/getstarted/>`_

`<https://docs.saltstack.com/en/latest/>`_

Get SaltStack Support and Help
==============================

**IRC Chat** - Join the vibrant, helpful and positive SaltStack chat room in
Freenode at #salt. There is no need to introduce yourself, or ask permission to
join in, just help and be helped! Make sure to wait for an answer, sometimes it
may take a few moments for someone to reply.

`<http://webchat.freenode.net/?channels=salt&uio=Mj10cnVlJjk9dHJ1ZSYxMD10cnVl83>`_

**Mailing List** - The SaltStack community users mailing list is hosted by
Google groups. Anyone can post to ask questions about SaltStack products and
anyone can help answer. Join the conversation!

`<https://groups.google.com/forum/#!forum/salt-users>`_

You may subscribe to the list without a Google account by emailing
salt-users+subscribe@googlegroups.com and you may post to the list by emailing
salt-users@googlegroups.com

**Reporting Issues** - To report an issue with Salt, please follow the
guidelines for filing bug reports:
`<https://docs.saltstack.com/en/develop/topics/development/reporting_bugs.html>`_

**SaltStack Support** - If you need dedicated, prioritized support, please
consider a SaltStack Support package that fits your needs:
`<http://www.saltstack.com/support>`_

Engage SaltStack
================

`SaltConf`_, **User Groups and Meetups** - SaltStack has a vibrant and `global
community`_ of customers, users, developers and enthusiasts. Connect with other
Salted folks in your area of the world, or join `SaltConf16`_, the SaltStack
annual user conference, April 19-21 in Salt Lake City. Please let us know if
you would like to start a user group or if we should add your existing
SaltStack user group to this list by emailing: info@saltstack.com

**SaltStack Training** - Get access to proprietary `SaltStack education
offerings`_ through instructor-led training offered on-site, virtually or at
SaltStack headquarters in Salt Lake City. SaltStack Enterprise training helps
increase the value and effectiveness of SaltStack software for any customer and
is a prerequisite for coveted `SaltStack Certified Engineer (SSCE)`_ status.
SaltStack training is also available through several `SaltStack professional
services`_ offerings.

**Follow SaltStack on -**

* YouTube - `<http://www.youtube.com/saltstack>`_
* Twitter - `<http://www.twitter.com/saltstack>`_
* Facebook - `<https://www.facebook.com/SaltStack/>`_
* LinkedIn - `<https://www.linkedin.com/company/salt-stack-inc>`_
* LinkedIn Group - `<https://www.linkedin.com/groups/4877160>`_
* Google+ - `<https://plus.google.com/b/112856352920437801867/+SaltStackInc/posts>`_

.. _SaltConf: http://www.youtube.com/user/saltstack
.. _global community: http://www.meetup.com/pro/saltstack/
.. _SaltConf16: http://saltconf.com/
.. _SaltStack education offerings: http://saltstack.com/training/
.. _SaltStack Certified Engineer (SSCE): http://saltstack.com/certification/
.. _SaltStack professional services: http://saltstack.com/services/

Developing Salt
===============

The Salt development team is welcoming, positive, and dedicated to
helping people get new code and fixes into SaltStack projects. Log into
GitHub and get started with one of the largest developer communities in
the world. The following links should get you started:

`<https://github.com/saltstack>`_

`<https://docs.saltstack.com/en/latest/topics/development/index.html>`_

`<https://docs.saltstack.com/en/develop/topics/development/pull_requests.html>`_