Integration test for remote stack

A test case that exercise the OS::Heat::Stack resource as part of the
integration tests.

Change-Id: Ib09a46f2ca7825e4190c3fb8c7c1510e95688a10
Add PropertyUnspecifiedError exception

If we have situation, when we must specify at
least one of two conflicted resources, and there
is no specified resource, we get StackValidationFailed
with error msg looks like 'Either resource_1 or
resource_2 must be specified'. There are a few places,
where this situation appears. So it will be reasonable
to add special exception for these situations.

Change-Id: Ib107eff4fe8030fdbb40aa267b9e2b394ff7a186
Check stack adopt enable before adopting

If the configuration is disabled, don't start to adopt.

Co-Authored-by: huangtianhua <huangtianhua@huawei.com>
Co-Authored-by: asalkeld <asalkeld@mirantis.com>

Change-Id: Iddb5024971f9f7882c5e46d879439182d2a92124
Closes-Bug: #1396917
Imported Translations from Transifex

For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: Ic2c92d4b044f725b43242ae32282d45ef770793b
Merge "Check stack adopt enable before adopting"
Merge "Integration test for remote stack"
Merge "Imported Translations from Transifex"
Move instance_error_causes_group_error() to functional tests

Part of blueprint decouple-nested
Change-Id: I33a9772642c6e58b4b9419330d2aa4e3f8e5cab4
Add some autoscaling crud unit tests

These are basic to get some coverage.

Part of blueprint decouple-nested
Change-Id: I764fedd4371a7a641df98a923b7616df6498c944
Remove duplicate test (it's already in our functional tests)

This test duplicates what is here:
https://github.com/openstack/heat/blob/master/heat_integrationtests/functional/test_update.py#L89-L133

But does not require a full nested stack in unit tests.

Part of blueprint decouple-nested

Change-Id: If5a9d6b1c9dd98b31966312af16587cd148b9c6b
Separate StackWatch out into it's own module

In the interest in small modules that have a matching unit test file.

Part of blueprint decouple-nested
Change-Id: Ia40310007113b1111883a20db99cb7f754ae43bf
Disable nested validation for ResourceGroup with zero count

Some users (TripleO specifically) want to disable features via a
count of zero, which is a problem as we always recurse and validate
the nested stack since c31c34f8dfd0919bf46a975701c139073115debc

Instead, we only do validation when the count is non-zero, to
enable, e.g default image names, to be ignored at validation
time (as we'll never use them) instead of rejected by the nested
schema (e.g the server.py properties schema which contains a
custom contraint to always validate the image).

This should still allow us to fail fast (at validation time before
creating anything) when we're actually about to create something,
e.g when the count is non-zero.

Change-Id: I411ff41a9e0730e9864f5ed4ac54f1d5d0ec02d7
Closes-Bug: #1401929
Merge "Add PropertyUnspecifiedError exception"
Fix json syntax in inline template

Change-Id: Ie70d5c75146e81b765edde611edef81805915a0c
Merge "Move instance_error_causes_group_error() to functional tests"
Merge "Add some autoscaling crud unit tests"
Merge "Remove duplicate test (it's already in our functional tests)"
Remove gettextutils import

Change-Id: I48846926cc5eb2a1f81db6a2becb310bdf61daa7
Closes-Bug: #1404206
Merge "Separate StackWatch out into it's own module"
Fix doc generation for contrib resources

Since we shouldn't require contrib resources to be installed in order to
generate documentation, this adds an exception to the plugin loader so
that it doesn't try to load the setup.py files that can be found inside
each plugin directory inside contrib/

Closes-Bug: 1403897
Change-Id: Id6ece4379599925dd17d22cef401c8d667a0ac51