Updates an existing Managed Service for Apache Flink application
Source:R/kinesisanalyticsv2_operations.R
kinesisanalyticsv2_update_application.RdUpdates an existing Managed Service for Apache Flink application. Using this operation, you can update application code, input configuration, and output configuration.
See https://www.paws-r-sdk.com/docs/kinesisanalyticsv2_update_application/ for full documentation.
Usage
kinesisanalyticsv2_update_application(
ApplicationName,
CurrentApplicationVersionId = NULL,
ApplicationConfigurationUpdate = NULL,
ServiceExecutionRoleUpdate = NULL,
RunConfigurationUpdate = NULL,
CloudWatchLoggingOptionUpdates = NULL,
ConditionalToken = NULL,
RuntimeEnvironmentUpdate = NULL
)Arguments
- ApplicationName
[required] The name of the application to update.
- CurrentApplicationVersionId
The current application version ID. You must provide the
CurrentApplicationVersionIdor theConditionalToken.You can retrieve the application version ID usingdescribe_application. For better concurrency support, use theConditionalTokenparameter instead ofCurrentApplicationVersionId.- ApplicationConfigurationUpdate
Describes application configuration updates.
- ServiceExecutionRoleUpdate
Describes updates to the service execution role.
- RunConfigurationUpdate
Describes updates to the application's starting parameters.
- CloudWatchLoggingOptionUpdates
Describes application Amazon CloudWatch logging option updates. You can only update existing CloudWatch logging options with this action. To add a new CloudWatch logging option, use
add_application_cloud_watch_logging_option.- ConditionalToken
A value you use to implement strong concurrency for application updates. You must provide the
CurrentApplicationVersionIdor theConditionalToken. You get the application's currentConditionalTokenusingdescribe_application. For better concurrency support, use theConditionalTokenparameter instead ofCurrentApplicationVersionId.- RuntimeEnvironmentUpdate
Updates the Managed Service for Apache Flink runtime environment used to run your code. To avoid issues you must:
Ensure your new jar and dependencies are compatible with the new runtime selected.
Ensure your new code's state is compatible with the snapshot from which your application will start