Re: [Discuss] Generate cert and key files automatically

[Yunze Xu]

I have another concern that since we have to use `AuthenticationTls` for TLS
transport encryption, how can we perform a non-TLS authentication? It looks
like there’s no way to do that.

Thanks,
Yunze




> 2022年3月23日 11:24，Zixuan Liu  写道：
> 
>> I think the priority of `AuthenticationTls` must be higher. Then it
> should be encouraged to use `AuthenticationTls` when TLS authentication is
> enabled at broker side. Otherwise, these two options should be encouraged
> to use.
> 
> You are right, if we are set up the `AuthenticationTls` and TLS transport,
> we should use the `AuthenticationTls` data to set up, `AuthenticationTls`
> must be higher. When the user set up two config, we need to throw an
> expectation that only use the `AuthenticationTls`, or `tlsCertFilePath` and
> `tlsKeyFilePath`.
> 
> 
> Yunze Xu  于2022年3月23日周三 01:57写道：
> 
>> If `tlsCertFilePath` and `tlsKeyFilePath` were added to the client builder
>> options, I think they can also be used for TLS authentication as well.
>> 
>> I prefer this solution now just because it looks like generating
>> certificats
>> automatically is not good, from what Enrico said.
>> 
>> The problem is that what if we configured both `AuthenticationTls` and
>> those
>> two options? Because the underlying mechanisms are the same that a
>> `SslContext`
>> is created from the cert and key files and then the `SslContext` object
>> will be
>> used in the TCP or HTTP transport.
>> 
>> I think the priority of `AuthenticationTls` must be higher. Then it should
>> be
>> encouraged to use `AuthenticationTls` when TLS authentication is enabled at
>> broker side. Otherwise, these two options should be encouraged to use.
>> 
>> Thanks,
>> Yunze
>> 
>> 
>> 
>> 
>>> 2022年3月22日 上午11:03，Zixuan Liu  写道：
>>> 
>>> Hi Yunze,
>>> 
>>> The current implementation is confusing, we should split the transport
>> and
>>> auth for TLS.
>>> 
>>> For transport, the code can be so like:
>>> ```
>>> PulsarClient client = PulsarClient.builder()
>>>   .enableTls(true)
>>>   .tlsTrustCertsFilePath("ca.pem")
>>>   .tlsCertFilePath("client-ca.pem")
>>>   .tlsKeyFilePath("client-key.pem")
>>>   .build();
>>> ```
>>> 
>>> For auth, the code can be so like:
>>> ```
>>> Map authParams = new HashMap<>();
>>> authParams.put("tlsCertFile", "client-ca.pem");
>>> authParams.put("tlsKeyFile", "client-key.pem");
>>> PulsarClient client = PulsarClient.builder()
>>>   .enableTls(true)
>>>   .tlsTrustCertsFilePath("ca.pem")
>>>   .authentication(AuthenticationTls.class.getName(),
>>> authParams)
>>>   .build();
>>> ```
>>> 
>>> When using the TLS auth, we don't need to set
>>> tlsCertFilePath("client-ca.pem") and tlsKeyFilePath("client-key.pem"),
>> the
>>> authentication instead of this.
>>> 
>>> There have an important thing that if we are using the authentication
>> with
>>> the token, we cannot setup the TLS transport.
>>> 
>>> 
>>> Enrico Olivelli  于2022年3月22日周二 00:40写道：
>>> 
 Il giorno lun 21 mar 2022 alle ore 16:31 Yunze Xu
  ha scritto:
> 
> Hi all,
> 
> Recently I found a document error when configuring Pulsar client for
>> TLS
> encryption. See https://github.com/apache/pulsar/issues/14762.
>> However,
 the code
> example in the official documents is more intuitive.
> 
> See
 https://pulsar.apache.org/docs/en/security-tls-transport/#java-client,
>> the
> example code doesn't configure `AuthenticationTls`, but it is required
 once TLS
> encryption is enabled, even if TLS authentication is not enabled.
 Because the
> client side can only send a SSL handshake via `AuthenticationTls`. It
 would be
> confused.
> 
> Since the cert file and the key file are generated using a CA, whose
 path is
> specified by `tlsTrustCertsFilePath` method, I think it would be
 possible to
> generate a cert and a key file automatically. We only need to specify a
 common
> name, which represents the role when authentication is enabled.
 
 Usually a service cannot generate a "valid" certificate automatically,
 it MUST be signed by a CA.
 
 We may add an option to automatically generate a certificate (and a
 CA) but that will work only for
 DEV environments.
 
 Enrico
 
 
> 
> My initial design is, when client configures the
>> `tlsTrustCertsFilePath`:
> - If no authentication plugin is enabled, generate the cert and key
>> files
> automatically using a default common name.
> - Otherwise, use the cert and key files specified in
>> `AuthenticationTls`.
> 
> The benefit is, when you want to pass the TLS authentication, you must
 configure
> `AuthenticationTls` at client side, while you only needs to configure
> `tlsTrustCertsFilePath` if broker side only enables TLS encryption.
> 
> What do you think? Is there a better solution?
> 

Re: [ANNOUNCE] New Committer: Zhangmin Gao

[r...@apache.org]

Congrats Zhangmin!

--
Thanks
Xiaolong Ran

Ran Gao  于2022年4月18日周一 13:41写道：

> +1
>
> Best,
> Ran Gao
>
> On 2022/04/13 09:35:57 PengHui Li wrote:
> > The Apache Pulsar Project Management Committee (PMC) has invited Zhangmin
> > Gao
> > https://github.com/gaozhangmin to become a committer and we are pleased
> to
> > announce that he has accepted.
> >
> > Welcome and Congratulations, Zhangmin Gao!
> >
> > Please join us in congratulating and welcoming Zhangmin Gao onboard!
> >
> > Best Regards,
> > Penghui Li on behalf of the Pulsar PMC
> >
>

Re: [ANNOUNCE] New Committer: Zike Yang

[ZhangJian He]

Congratulations

Thanks
ZhangJian He

Ran Gao  于2022年4月18日周一 13:33写道：

> Hi, zike, congratulations!
>
> Ran Gao
>
> Best
>
> On 2022/04/13 09:34:23 PengHui Li wrote:
> > The Apache Pulsar Project Management Committee (PMC) has invited Zike
> Yang
> > https://github.com/RobertIndie to become a committer and we are pleased
> to
> > announce that he has accepted.
> >
> > Welcome and Congratulations, Zike Yang!
> >
> > Please join us in congratulating and welcoming Zike Yang onboard!
> >
> > Best Regards,
> > Penghui Li on behalf of the Pulsar PMC
> >
>

Re: [ANNOUNCE] New Committer: Ruguo Yu

[ZhangJian He]

Congratulations

Thanks
ZhangJian He

Ran Gao  于2022年4月18日周一 13:34写道：

> Congratulations!
>
> Ran
>
> Best
>
> On 2022/04/15 10:06:44 Yu wrote:
> > The Apache Pulsar Project Management Committee (PMC) has invited Ruguo
> Yu (
> > https://github.com/yuruguo) to become a committer and we are pleased to
> > announce that he has accepted.
> >
> > Welcome and Congratulations, Ruguo Yu!
> >
> > Please join us in congratulating and welcoming Ruguo Yu onboard!
> >
> > Best Regards,
> >
> > Yu on behalf of the Pulsar PMC
> >
>

Re: [ANNOUNCE] New Committer: Zhangmin Gao

[ZhangJian He]

Congratulations

Thanks
ZhangJian He

r...@apache.org  于2022年4月18日周一 16:59写道：

> Congrats Zhangmin!
>
> --
> Thanks
> Xiaolong Ran
>
> Ran Gao  于2022年4月18日周一 13:41写道：
>
> > +1
> >
> > Best,
> > Ran Gao
> >
> > On 2022/04/13 09:35:57 PengHui Li wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited
> Zhangmin
> > > Gao
> > > https://github.com/gaozhangmin to become a committer and we are
> pleased
> > to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Zhangmin Gao!
> > >
> > > Please join us in congratulating and welcoming Zhangmin Gao onboard!
> > >
> > > Best Regards,
> > > Penghui Li on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] Apache Pulsar 2.9.2 released

[tamer Abdlatif]

The release notes refers to 2.10.0 instead of 2.9.2

Thanks
Tamer

On Mon, 18 Apr 2022, 07:25 Ran Gao,  wrote:

> The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.2.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, it also provides transaction
> feature since 2.8.0, guaranteed exactly-once semantics for producing and
> consuming process over topics, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> For Pulsar release details and downloads, visit:
>
> https://pulsar.apache.org/download
>
> Release Notes are at:
> https://pulsar.apache.org/release-notes
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The Pulsar Team
>

Categorize Pulsar Plugins

[Yu]

Hi Pulsarers,


For the Ecosystem Page [1], we want to make it a place for the Pulsar
community to come together and share the components the community needs to
build better streaming data pipelines and event-driven applications.


So I've collected all Pulsar-related plugins and tried to re-categorize
them **based on scenarios**.


For the "Components Managed by DataStax", does anyone can help review the
"Category"? [2] We're unsure about it.


Feel free to review the whole sheet and comment if I miss or misunderstand
anything, thank you!


[1] https://pulsar-next.staged.apache.org/ecosystem/

[2]
https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0


Anonymitaet

PIP-156: Build and Run Pulsar Server on Java 17

[Heesung Sohn]

Dear Pulsar dev community,

My name is Heesung Sohn, and I would like to open a discussion here
about PIP-156:
Build and Run Pulsar Server on Java 17
.


@Nicolò Boschi,
I see your similar PR  for the
Java 17 runtime support. Since some of the Java 17 upgrade work could
overlap, it would be great if we can discuss how to collaborate too -- for
this PIP, we need to additionally update the `javac --release` option to
Java 17.

Regards,
Heesung
-- 



Heesung Sohn

Platform Engineer

e: heesung.s...@streamnative.io

streamnative.io

Re: [ANNOUNCE] Apache Pulsar 2.9.2 released

[PengHui Li]

https://pulsar.apache.org/release-notes/#292

This one is for 2.9.2

Thanks,
Penghui

On Mon, Apr 18, 2022 at 6:34 PM tamer Abdlatif 
wrote:

> The release notes refers to 2.10.0 instead of 2.9.2
>
> Thanks
> Tamer
>
> On Mon, 18 Apr 2022, 07:25 Ran Gao,  wrote:
>
> > The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.2.
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at-least-once delivery of messages, it also provides
> transaction
> > feature since 2.8.0, guaranteed exactly-once semantics for producing and
> > consuming process over topics, automatic cursor management for
> > subscribers, and cross-datacenter replication.
> >
> > For Pulsar release details and downloads, visit:
> >
> > https://pulsar.apache.org/download
> >
> > Release Notes are at:
> > https://pulsar.apache.org/release-notes
> >
> > We would like to thank the contributors that made the release possible.
> >
> > Regards,
> >
> > The Pulsar Team
> >
>

Re: [ANNOUNCE] New Committer: Zike Yang

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> Ran Gao  于2022年4月18日周一 13:33写道：
>
> > Hi, zike, congratulations!
> >
> > Ran Gao
> >
> > Best
> >
> > On 2022/04/13 09:34:23 PengHui Li wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited Zike
> > Yang
> > > https://github.com/RobertIndie to become a committer and we are
> pleased
> > to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Zike Yang!
> > >
> > > Please join us in congratulating and welcoming Zike Yang onboard!
> > >
> > > Best Regards,
> > > Penghui Li on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] New Committer: Ruguo Yu

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> Ran Gao  于2022年4月18日周一 13:34写道：
>
> > Congratulations!
> >
> > Ran
> >
> > Best
> >
> > On 2022/04/15 10:06:44 Yu wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited Ruguo
> > Yu (
> > > https://github.com/yuruguo) to become a committer and we are pleased
> to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Ruguo Yu!
> > >
> > > Please join us in congratulating and welcoming Ruguo Yu onboard!
> > >
> > > Best Regards,
> > >
> > > Yu on behalf of the Pulsar PMC
> > >
> >
>

Re: [ANNOUNCE] New Committer: Zhangmin Gao

[guo jiwei]

Congrats


Regards
Jiwei Guo (Tboy)


On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:

> Congratulations
>
> Thanks
> ZhangJian He
>
> r...@apache.org  于2022年4月18日周一 16:59写道：
>
> > Congrats Zhangmin!
> >
> > --
> > Thanks
> > Xiaolong Ran
> >
> > Ran Gao  于2022年4月18日周一 13:41写道：
> >
> > > +1
> > >
> > > Best,
> > > Ran Gao
> > >
> > > On 2022/04/13 09:35:57 PengHui Li wrote:
> > > > The Apache Pulsar Project Management Committee (PMC) has invited
> > Zhangmin
> > > > Gao
> > > > https://github.com/gaozhangmin to become a committer and we are
> > pleased
> > > to
> > > > announce that he has accepted.
> > > >
> > > > Welcome and Congratulations, Zhangmin Gao!
> > > >
> > > > Please join us in congratulating and welcoming Zhangmin Gao onboard!
> > > >
> > > > Best Regards,
> > > > Penghui Li on behalf of the Pulsar PMC
> > > >
> > >
> >
>

[VOTE] [PIP-152] Support subscription level dispatch rate limiter setting.

[Haiting Jiang]

Hi Pulsar community,

This is the voting thread for PIP-152. It will stay open for at least 48 hours.

The proposal can be found: https://github.com/apache/pulsar/issues/15094

Discuss thread: https://lists.apache.org/thread/r6dzr09lc42yh79vt0dvmvlv6wtz2czn

Thanks,
Haiting Jiang

Re: [DISCUSS] [PIP-154] Max active transaction limitation for transaction coordinator

[Haiting Jiang]

Hi Bo,

Do we have metrics like "active transaction usage percent" to  set up monitor 
and alert.
This is necessary since this critical once the limitation is reached.

Thanks,
Haiting

On 2022/04/12 12:44:36 丛搏 wrote:
> pipHi Pulsar community,
> 
> I open a pip to discuss Max active transaction limitation for
> transaction coordinator.
> link: https://github.com/apache/pulsar/issues/15133
> 
> 
> Thanks,
> Bo
> 

[GitHub] [pulsar-manager] urfreespace opened a new pull request, #457: fix: dependencies fix for webpack and npm version limit

[GitBox]

urfreespace opened a new pull request, #457:
URL: https://github.com/apache/pulsar-manager/pull/457

   *(If this PR fixes a github issue, please add `Fixes #`.)*
   
   fix: dependencies fix for webpack and npm version limit
   
   *(or if this PR is one task of a github issue, please add `Master Issue: 
#` to link to the master issue.)*
   
   Master Issue: #
   
   ### Motivation
   
   
   *Explain here the context, and why you're making that change. What is the 
problem you're trying to solve.*
   
   ### Modifications
   
   *Describe the modifications you've done.*
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the `./gradlew build` checks.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-manager] urfreespace merged pull request #457: fix: dependencies fix for webpack and npm version limit

[GitBox]

urfreespace merged PR #457:
URL: https://github.com/apache/pulsar-manager/pull/457


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [ANNOUNCE] New Committer: Zhangmin Gao

[Li Li]

Congratulations!



> On Apr 19, 2022, at 09:44, guo jiwei  wrote:
> 
> Congrats
> 
> 
> Regards
> Jiwei Guo (Tboy)
> 
> 
> On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He  wrote:
> 
>> Congratulations
>> 
>> Thanks
>> ZhangJian He
>> 
>> r...@apache.org  于2022年4月18日周一 16:59写道：
>> 
>>> Congrats Zhangmin!
>>> 
>>> --
>>> Thanks
>>> Xiaolong Ran
>>> 
>>> Ran Gao  于2022年4月18日周一 13:41写道：
>>> 
 +1
 
 Best,
 Ran Gao
 
 On 2022/04/13 09:35:57 PengHui Li wrote:
> The Apache Pulsar Project Management Committee (PMC) has invited
>>> Zhangmin
> Gao
> https://github.com/gaozhangmin to become a committer and we are
>>> pleased
 to
> announce that he has accepted.
> 
> Welcome and Congratulations, Zhangmin Gao!
> 
> Please join us in congratulating and welcoming Zhangmin Gao onboard!
> 
> Best Regards,
> Penghui Li on behalf of the Pulsar PMC
> 
 
>>> 
>> 

[GitHub] [pulsar-test-infra] dependabot[bot] opened a new pull request, #31: Bump minimist from 1.2.5 to 1.2.6 in /test-reporter/reports/jest

[GitBox]

dependabot[bot] opened a new pull request, #31:
URL: https://github.com/apache/pulsar-test-infra/pull/31

   Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
   
   Commits
   
   https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846";>7efb22a
 1.2.6
   https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2";>ef88b93
 security notice for additional prototype pollution issue
   https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d";>c2b9819
 isConstructorOrProto adapted from PR
   https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb";>bc8ecee
 test from prototype pollution PR
   See full diff in https://github.com/substack/minimist/compare/1.2.5...1.2.6";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=minimist&package-manager=npm_and_yarn&previous-version=1.2.5&new-version=1.2.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   - `@dependabot use these labels` will set the current labels as the default 
for future PRs for this repo and language
   - `@dependabot use these reviewers` will set the current reviewers as the 
default for future PRs for this repo and language
   - `@dependabot use these assignees` will set the current assignees as the 
default for future PRs for this repo and language
   - `@dependabot use this milestone` will set the current milestone as the 
default for future PRs for this repo and language
   
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/pulsar-test-infra/network/alerts).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-test-infra] dependabot[bot] opened a new pull request, #32: Bump minimist from 1.2.5 to 1.2.6 in /test-reporter

[GitBox]

dependabot[bot] opened a new pull request, #32:
URL: https://github.com/apache/pulsar-test-infra/pull/32

   Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
   
   Commits
   
   https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846";>7efb22a
 1.2.6
   https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2";>ef88b93
 security notice for additional prototype pollution issue
   https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d";>c2b9819
 isConstructorOrProto adapted from PR
   https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb";>bc8ecee
 test from prototype pollution PR
   See full diff in https://github.com/substack/minimist/compare/1.2.5...1.2.6";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=minimist&package-manager=npm_and_yarn&previous-version=1.2.5&new-version=1.2.6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   - `@dependabot use these labels` will set the current labels as the default 
for future PRs for this repo and language
   - `@dependabot use these reviewers` will set the current reviewers as the 
default for future PRs for this repo and language
   - `@dependabot use these assignees` will set the current assignees as the 
default for future PRs for this repo and language
   - `@dependabot use this milestone` will set the current milestone as the 
default for future PRs for this repo and language
   
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/pulsar-test-infra/network/alerts).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org