The example here contradicted the preceding paragraph, which explains that you should either use include/exclude, or artifact, but not both. However the example then shows the use of include, exclude and artifact all together.
To resolve, I removed the include and exclude options from the example.
The removed paragraph refers to providing credentials instructions for multiple different cloud providers, whereas this doc is for AWS credentials only.
It seems likely that this paragraph was written at a time when there was a single document to cover credentials for all providers, but now that each provider has its own credentials doc, it no longer makes sense, and was probably left in place by accident.
Replace the existing service and clear the cache (which references the ammended service)
Remove cycles in that service using json-cycle.
Dump the decycled object as YAML to console.
Remove the errant (but understandable) distributed usage of region and stage settings. This otherwise locks in a multitude of bugs around the improper algorithm for selecting (given all context) the proper region or stage setting. Instead, all code should use the centralized algorithm for determining such values. This creates a strange first and second class configuration concept but these two are sufficiently varied and complex in their creation and use that this seems appropriate.
Delete bucket was still using them
Hopefully all :)
Further test fixes.
.... worked too long yesterday
Fixed Variable tests
Remove not used parameters from request() and add options with warning
1. add tests that validate string value defaults in overrides.
2. add test of behavior when a javascript's export does not contain the attribute declared in the variable.
3. add tests of behavior when an SSM parameter is not found and the request to the SSM service fails.
add returns to tests that weren't returning their promises (and were thereby risking false positives.
Increase name consistency
Improve names to be-what-they-are
Reduce cyclomatic complexity
Include overrides population fix
Add variable methods documentation
Add more tests around significant variable patterns/risky cases
