cloudtools / cloudtools/stacker

AWS parameter type name instead of CFNType

Open
#546 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
707
Forks
162
PR merge metrics
No merged PRs in 30d

Description

Right now, if you want to specify a variable as a CloudFormation parameter, you would import the appropriate CFNType, then use that as the type field. For example:

```python
from stacker.blueprints.variables.types import EC2VPCId

VARIABLES = {
"VpcId": {
"type": EC2VPCId
}
}
```

This works fine, but I think we could make a little simpler and easier to use. If instead, you could do the following:

```python
VARIABLES = {
"VpcId": {
"type": "AWS::EC2::VPC::Id"
}
}
```

And stacker would internally convert it to a `EC2VPCId`. This behavior would be pretty similar to what we had in 0.8.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.