[Bug fix] run_configuration
not part of update request resulting in default values
#42387
+297
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
AWS Managed Flink application allows mechanism to configure the runtime configuration that part of
run_configuration
attribute.During the
UpdateApplication
workflow, if there is no change in therun_configuration
the values are not passed with the Update request. This results in AWS setting them to default value.Applications fail to start after updates when
run_configuration.flink_run_configuration.allow_non_restored_state
is defined astrue
. As this parameter isn't being properly preserved, the AWS default value isfalse
, causing applications that require this setting to fail during update.Output from Acceptance Testing
New acceptance test added
TestAccKinesisAnalyticsV2Application_FlinkApplication_updateRestorable
for verifying the run_configuration across updates.