Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

!GetAtt DocDB::Cluster.Port is reporting as an integer #3757

Closed
kddejong opened this issue Oct 17, 2024 · 2 comments · Fixed by #3759
Closed

!GetAtt DocDB::Cluster.Port is reporting as an integer #3757

kddejong opened this issue Oct 17, 2024 · 2 comments · Fixed by #3759

Comments

@kddejong
Copy link
Contributor

          @kddejong after this change, it's not clear to me how we're supposed to Output for example an RDS DBCluster's Port, which is a number.

Value: !GetAtt DBCluster.Port fails with E6101
Attempting to cast it with something like Value: !Sub ${DBCluster.Port} also fails with E6101

Unless that is something that changed very recently, CloudFormation used to happily accept Value: !GetAtt DBCluster.Port

Originally posted by @Dantemss in #3725 (comment)

@Dantemss
Copy link

Dantemss commented Oct 17, 2024

@kddejong kddejong reopened this Oct 17, 2024
@kddejong kddejong changed the title !GetAtt DBCluster.Port is reporting as an integer !GetAtt DocDB::Cluster.Port is reporting as an integer Oct 17, 2024
@kddejong
Copy link
Contributor Author

kddejong commented Oct 17, 2024

This property is an exception. We currently assume that the type for these exceptions matches to the schema definition but that isn't true in this case. Working on a fix.

To be clear its an exception in which the schema doesn't properly define it and we try to fix that missing attribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants