Skip to content

IGNITE-18945 Add an ability to extend control-utility with the new commands - #10576

Closed
alex-plekhanov wants to merge 5 commits into
apache:masterfrom
alex-plekhanov:ignite-18945
Closed

IGNITE-18945 Add an ability to extend control-utility with the new commands#10576
alex-plekhanov wants to merge 5 commits into
apache:masterfrom
alex-plekhanov:ignite-18945

Conversation

@alex-plekhanov

Copy link
Copy Markdown
Contributor

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

new CommandsProviderImpl().commands().forEach((k, v) -> cmds.put(k.toLowerCase(), v));

if (!F.isEmpty(it)) {
for (CommandsProvider provider : it) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems useful to add logging of what exeternal commands were registered.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There can be tools which parse the output of control.sh script and new unexpected output can break these tools. At least for "info" logging level. But we can use "debug" logging level.

@asfgit asfgit closed this in 0f91ab2 Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants