Angus McInnes

I created a change set with type IMPORT, using the AWS CLI. When applying this change set with stackup, the final state of the stack is `IMPORT_COMPLETE`. This is a...

My team has some projects which involve deploying about 10 stacks in parallel to the same AWS account and region. If we deploy multiple of these projects at once we...

Fails to create change sets when a stack is in the REVIEW_IN_PROGRESS state

5

Using stackup 1.2.0 If I do `change-set create` against a stack that doesn't exist, a stack is created in the `REVIEW_IN_PROGRESS` state, as expected. If I then try to create...

Poetry with `virtualenvs.create false` installs packages into the wrong place on Ubuntu

41

- [x] I am on the [latest](https://github.com/python-poetry/poetry/releases/latest) Poetry version. - [x] I have searched the [issues](https://github.com/python-poetry/poetry/issues) of this repo and believe that this is not a duplicate. - [x] If...

The `be_served_from_origin` checks the hostname in the cache key, and assumes this is going to be the origin hostname. If you set cache key to incoming host header, `be_served_from_origin` will...

I think Stackup transforms `!Condition foo` into `{"Fn::Condition": "foo"}` when it should just be `{"Condition": "foo"}`. This breaks nested conditions such as the YAML example at the bottom of [this...