-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support Condition Functions #222
Conversation
I'm running into casing problems here now:
I think we're sending incorrect-cased sub-properties to aws-native. Digging in a bit, not sure if preexisting problem or something introduced just here. |
This depends on #228 but once that is in hopefully can pass integration tests here. |
f939352
to
32e16d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks much better than what we have, love the separate functions for each intrinsic!
My only nit comments are around adding docstrings to the methods that are missing them. I've commented on a couple, but it applies to all of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it!
@@ -543,6 +544,18 @@ export class StackConverter extends ArtifactConverter { | |||
}, this.processIntrinsics(params)); | |||
} | |||
|
|||
case 'Fn::Equals': { | |||
return intrinsics.fnEquals.evaluate(this, params); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having separate functions for each intrinsic is much more understandable. Love it!
|
||
/** | ||
* Production code may have intermediate values occasionally wrapped in pulumi.Output<T>; this is currently somewhat | ||
* difficult to test, so the essentials of pulumi.Output<T> are abstracted into a Result<T>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite understand this. Right now it's just any
, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's pulumi.Output<T>
in prod, but TestResult<T>
in test. I could have used pulumi.Output<T>
but currently testing failing scenarios there is very annoying.
Support Condition Functions.
Fixes #206
With this change, if CDK emits CF templates with Condition Functions, pulumi-cdk evaluates these. This unlocks support for new constructs such as the Kinesis Stream construct.