Issues
- 2
- 2
Sceptre launch exit code 1
#1339 opened - 1
Stack differ raises if a value is None
#1336 opened - 4
- 1
Add a dump vars command
#1334 opened - 0
refactor sceptre docs deployments
#1327 opened - 1
- 3
InternalFailure during UpdateStack
#1320 opened - 2
- 1
- 1
- 16
- 3
- 1
All errors related to a specific stack should include the stack name in the error message.
#1306 opened - 0
Logs out of Template Handlers, Hooks, and Resolvers don't indicate what stack they're operating on
#1304 opened - 2
ConnectionManager's call() method is too easy to misuse by not passing enough variables.
#1299 opened - 19
We have a bunch of hooks, resolvers, and other junk in the Sceptre Org nobody knows about
#1298 opened - 0
- 6
Intermittent AttributeError when resolving dependencies using the sceptre.plan.plan module.
#1291 opened - 6
- 1
Assume iam_role BEFORE resolving parameters
#1289 opened - 1
- 7
Add coloured deep diffs
#1279 opened - 9
Adopt Black for Automatic Code Formatting
#1276 opened - 6
Packaged Template Management
#1274 opened - 4
Events missing from launch output
#1273 opened - 0
Some CloudFormation states are not coloured
#1271 opened - 1
When a non-existent Stack is Launched, the List of Valid Stack Paths is not useful in a Large Workspace
#1268 opened - 3
- 2
- 7
- 11
iam_role is ignored for dependencies
#1262 opened - 0
Add coloured diffs
#1261 opened - 3
- 5
Add Bucket Policy to Sceptre's template bucket
#1255 opened - 1
Better error handling with invalid templates
#1253 opened - 1
- 1
- 3
- 0
- 2
Getting region from config.yaml
#1237 opened - 2
Update `networkx` to mitigate CWE-502
#1236 opened - 2
Vars overwrite not working
#1235 opened - 3
An empty var file causes Sceptre to blow up
#1234 opened - 7
Add Python 3.10 support
#1225 opened - 1
- 5
- 5
'YAML not well-formed' error when having comments before the start of document line `---`
#1222 opened - 0
- 5
_update _create hooks acting like _launch
#1215 opened