feat(cloud::zscaler::ztb::restapi): new plugin

[omercier]

Description

New plugin developed by @garnier-quentin (originally committed in #6319).

Refs: CTOR-2448

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Functionality enhancement or optimization (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

Robot tests provided.

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (develop).
• In case of a new plugin, I have created the new packaging directory accordingly.
• I have implemented automated tests related to my commits.
  • Data used for automated tests are anonymized.
• I have reviewed all the help messages in all the .pm files I have modified.
  • All sentences begin with a capital letter.
  • All sentences end with a period.
  • I am able to understand all the help messages, if not, exchange with the PO or TW to rewrite them.
• After having created the PR, I will make sure that all the tests provided in this PR have run and passed.

[garnier-quentin]

@omercier it's important to not remove the change on file:
src/centreon/plugins/templates/counter.pm

sub custom_output {
    my ($self, %options) = @_;

    my $value = $self->{option_results}->{ $options{option} };
    $value =~ s/%\(([a-zA-Z0-9\._:\-]+?)\)/$options{values}->{$1}/g;
    return $value;
}

Moreover, i'll add a enhancement today for the interface discovery

[omercier]

@omercier it's important to not remove the change on file: src/centreon/plugins/templates/counter.pm

sub custom_output {
    my ($self, %options) = @_;

    my $value = $self->{option_results}->{ $options{option} };
    $value =~ s/%\(([a-zA-Z0-9\._:\-]+?)\)/$options{values}->{$1}/g;
    return $value;
}

Moreover, i'll add a enhancement today for the interface discovery

Hi @garnier-quentin,
I have removed the function but I believe the functionality it supported is still working.
Can you explain why you would like to keep it rather than using the placeholders I put instead?

[garnier-quentin]

Hi @garnier-quentin, I have removed the function but I believe the functionality it supported is still working. Can you explain why you would like to keep it rather than using the placeholders I put instead?

If it works the same. it's ok for me.

I tell you when it's ok for the enhancement

[omercier]

Hi @garnier-quentin, I have removed the function but I believe the functionality it supported is still working. Can you explain why you would like to keep it rather than using the placeholders I put instead?

If it works the same. it's ok for me.

👍🏻

I tell you when it's ok for the enhancement

We've planned to release on next monday. Can you push it in a new PR for another release?

[omercier]

BTW @garnier-quentin, the output of cluser-appconnector mode lacks the debug data. If you have the possibility to send it I'll add it to the tests later

[garnier-quentin]

BTW @garnier-quentin, the output of cluser-appconnector mode lacks the debug data. If you have the possibility to send it I'll add it to the tests later

I have added the file in the ticket

[garnier-quentin]

@omercier could you add the last changes about that plugin: garnier-quentin@b1f7cbd

[thibaults-centreon]

est ce qu'on ne devrait pas plutot mettre gateway.container.cpu.utilization.percentage ? (ou container tout court)
idem L123 pour memory

[thibaults-centreon]

la syntaxe n'est pas uniquement avec des parenthèses %(sitename) pour cette option ?