-
Notifications
You must be signed in to change notification settings - Fork 95
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
Replace "run now" CustomAction with standard action PerformSingleExecution #7165
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
...src/main/scala/pl/touk/nussknacker/engine/api/deployment/ProcessStateDefinitionManager.scala
Show resolved
Hide resolved
extensions-api/src/main/scala/pl/touk/nussknacker/engine/api/deployment/ProcessAction.scala
Outdated
Show resolved
Hide resolved
879fd84
to
d3c0e7d
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.
Minor comments added
...gner/client/src/components/toolbars/scenarioActions/buttons/PerformSingleExecutionButton.tsx
Outdated
Show resolved
Hide resolved
...manager-api/src/main/scala/pl/touk/nussknacker/engine/api/deployment/DMScenarioCommand.scala
Show resolved
Hide resolved
disabled={name === "run now" ? disabledValue : false} | ||
type={type} | ||
/> | ||
<CustomActionButton action={action} processName={processName} disabled={false} processStatus={status} type={type} /> |
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.
As I see, there is no option to disable a custom action based on FE types. Do we need this disabled
flag?
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 is part of common ToolbarButtonProps
, used for all buttons. AFAIK this value must be provided. I guess at the moment it is the only button, that is never disabled on FE side, so constant false
provided here
After Arek's comments I added internationalization of tooltip messages, I think it needs FE review too. <-this change is reverted
This reverts commit aeaec47
…ate-handling # Conflicts: # docs/Changelog.md # docs/MigrationGuide.md
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.
PeriodicProcessServiceIntegrationTest
failed. Is it related with your change?
Seems completely not related. My change did not modify how periodic processes work internally. Logs are not conclusive, but I think it was Flink deployment error that caused it. It passes locally and passed on retry. |
OK, so let's merge it |
Describe your changes
The main purpose of this PR, is to refactor "run now" action for periodic DeploymentManagers:
Planned changes related to the PeriodicDeploymentManager:
1A. Completely remove CustomAction mechanism, as it will be unused after stage 1 "run now"
Most important changes:
actions
panel, no longer uses generic CustomAction mechanism and buttondef applicableActions
) (right now only applied to "run now" for periodic processes)Checklist before merge
Summary by CodeRabbit
New Features
PerformSingleExecution
action, now supported in the DeploymentManager and GUI.DMPerformSingleExecutionCommand
for processing single execution requests.PerformSingleExecutionButton
added to the toolbar for executing single actions.Bug Fixes
Documentation