-
Notifications
You must be signed in to change notification settings - Fork 4k
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
appsync - apiKeyConfig expires outputting incorrect format #8698
Comments
According to the definition:
WorkaroundYou should set Use Proposed solutionBut in fact, it is also prone to errors and needs to be changed in a different way.
Any good idea? |
What about using kind of AS-IS
TO-BE
ReferencesI hope the things below would be promoted to Expiresaws-cdk/packages/@aws-cdk/aws-s3-deployment/lib/bucket-deployment.ts Lines 318 to 344 in 254556d
Schedule
|
**[ISSUE]** `apiKeyConfig` has prop `expires` that has unclear documentation/not strongly typed and is prone to user errors. **[APPROACH]** Force `expires` to take `Expiration` class from `core` and will be able to output api key configurations easily through `Expiration` static functions: `after(...)`, `fromString(...)`, ` atDate(...)`, `atTimeStamp(...)`. Fixes #8698 BREAKING CHANGE: force `apiKeyConfig` require a Expiration class instead of string - **appsync**: Parameter `apiKeyConfig` takes `Expiration` class instead of `string` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When specifying the attribute "expires" for apiKeyConfig, the rendered cloudformation gets a value of null.
Reproduction Steps
Error Log
Synth gives:
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: