Skip to content
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

chore(deps): update dependency @pulumi/azure-native to v2.85.0 #2016

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pulumi/azure-native (source) 2.84.0 -> 2.85.0 age adoption passing confidence

Release Notes

pulumi/pulumi-azure-native (@​pulumi/azure-native)

v2.85.0

Compare Source

Does the PR have any schema changes?

Looking good! No breaking changes found.

New resources:
  • network.DnssecConfig
  • network.NetworkVirtualApplianceConnection
New functions:
  • network.getDnssecConfig
  • network.getNetworkVirtualApplianceConnection

What's Changed

Full Changelog: pulumi/pulumi-azure-native@v2.84.0...v2.85.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 30, 2025
Copy link

coderabbitai bot commented Jan 30, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@benchmarks/node-fetch results (noConsumeBody)

   ✓ active_handles.................: avg=139.942418 min=12     med=141     max=198     p(90)=160     p(95)=165    
     data_received..................: 21 MB  715 kB/s
     data_sent......................: 14 MB  463 kB/s
     http_req_blocked...............: avg=4.09µs     min=621ns  med=1.45µs  max=8.82ms  p(90)=2.05µs  p(95)=2.35µs 
     http_req_connecting............: avg=2.09µs     min=0s     med=0s      max=6.82ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=21.32ms    min=3.12ms med=20.7ms  max=1.11s   p(90)=27.02ms p(95)=28.68ms
       { expected_response:true }...: avg=21.32ms    min=3.12ms med=20.7ms  max=1.11s   p(90)=27.02ms p(95)=28.68ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 140204
     http_req_receiving.............: avg=35.82µs    min=9.65µs med=24.86µs max=18.71ms p(90)=39.85µs p(95)=47.45µs
     http_req_sending...............: avg=12.22µs    min=3.53µs med=7.19µs  max=18.09ms p(90)=10.4µs  p(95)=14.7µs 
     http_req_tls_handshaking.......: avg=0s         min=0s     med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=21.27ms    min=3.09ms med=20.66ms max=1.11s   p(90)=26.97ms p(95)=28.61ms
     http_reqs......................: 140204 4672.687572/s
     iteration_duration.............: avg=42.76ms    min=9.38ms med=41.32ms max=1.14s   p(90)=46.99ms p(95)=52.06ms
     iterations.....................: 70074  2335.410608/s
     vus............................: 95     min=95        max=100 
     vus_max........................: 100    min=100       max=100 

Copy link
Contributor

@benchmarks/node-fetch results (consumeBody)

   ✓ active_handles.................: avg=140.172952 min=14       med=141     max=190     p(90)=159     p(95)=163    
     data_received..................: 20 MB  674 kB/s
     data_sent......................: 13 MB  432 kB/s
     http_req_blocked...............: avg=2.35µs     min=591ns    med=1.45µs  max=3.56ms  p(90)=2.16µs  p(95)=2.53µs 
     http_req_connecting............: avg=430ns      min=0s       med=0s      max=3.08ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=22.63ms    min=850.72µs med=21.97ms max=1.2s    p(90)=28.43ms p(95)=30.43ms
       { expected_response:true }...: avg=22.63ms    min=850.72µs med=21.97ms max=1.2s    p(90)=28.43ms p(95)=30.43ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 132076
     http_req_receiving.............: avg=39.55µs    min=10.54µs  med=26.75µs max=20.59ms p(90)=41.09µs p(95)=48.69µs
     http_req_sending...............: avg=12.21µs    min=3.63µs   med=7.19µs  max=27.6ms  p(90)=10.73µs p(95)=14.92µs
     http_req_tls_handshaking.......: avg=0s         min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=22.58ms    min=763.5µs  med=21.93ms max=1.2s    p(90)=28.37ms p(95)=30.36ms
     http_reqs......................: 132076 4402.100397/s
     iteration_duration.............: avg=45.39ms    min=6.58ms   med=43.76ms max=1.23s   p(90)=49.71ms p(95)=55.33ms
     iterations.....................: 66024  2200.583578/s
     vus............................: 100    min=100       max=100 
     vus_max........................: 100    min=100       max=100 

Copy link
Contributor

@benchmarks/server results (ponyfill)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 302360      ✗ 0     
     data_received..................: 30 MB   993 kB/s
     data_sent......................: 12 MB   403 kB/s
     http_req_blocked...............: avg=1.34µs   min=872ns    med=1.15µs   max=287.37µs p(90)=1.83µs   p(95)=2.01µs  
     http_req_connecting............: avg=0ns      min=0s       med=0s       max=137.47µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=138.14µs min=94.01µs  med=133.09µs max=7.02ms   p(90)=155.63µs p(95)=163.39µs
       { expected_response:true }...: avg=138.14µs min=94.01µs  med=133.09µs max=7.02ms   p(90)=155.63µs p(95)=163.39µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 151180
     http_req_receiving.............: avg=24.23µs  min=10.79µs  med=22.73µs  max=2.85ms   p(90)=30.1µs   p(95)=33.02µs 
     http_req_sending...............: avg=6.03µs   min=3.91µs   med=5.17µs   max=1.13ms   p(90)=7.94µs   p(95)=8.58µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=107.87µs min=69.34µs  med=102.58µs max=6.98ms   p(90)=121.87µs p(95)=128.32µs
     http_reqs......................: 151180  5039.111655/s
     iteration_duration.............: avg=194.13µs min=138.47µs med=188.25µs max=7.23ms   p(90)=214.83µs p(95)=224.62µs
     iterations.....................: 151180  5039.111655/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

Copy link
Contributor

@benchmarks/server results (undici)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 221026      ✗ 0     
     data_received..................: 22 MB   740 kB/s
     data_sent......................: 8.8 MB  295 kB/s
     http_req_blocked...............: avg=1.33µs   min=831ns    med=1.14µs   max=270.84µs p(90)=1.81µs   p(95)=1.97µs  
     http_req_connecting............: avg=1ns      min=0s       med=0s       max=131.11µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=210.44µs min=153.6µs  med=198.33µs max=60.44ms  p(90)=226.68µs p(95)=237.02µs
       { expected_response:true }...: avg=210.44µs min=153.6µs  med=198.33µs max=60.44ms  p(90)=226.68µs p(95)=237.02µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 110513
     http_req_receiving.............: avg=25.04µs  min=10.91µs  med=23.24µs  max=1.86ms   p(90)=30.47µs  p(95)=33.79µs 
     http_req_sending...............: avg=6.12µs   min=3.96µs   med=5.27µs   max=299.05µs p(90)=7.97µs   p(95)=8.47µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=179.27µs min=131µs    med=167.38µs max=60.36ms  p(90)=191.95µs p(95)=200.78µs
     http_reqs......................: 110513  3683.631187/s
     iteration_duration.............: avg=267.08µs min=195.54µs med=254µs    max=60.6ms   p(90)=285.81µs p(95)=299.08µs
     iterations.....................: 110513  3683.631187/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

Copy link
Contributor

@benchmarks/server results (native)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 207172      ✗ 0     
     data_received..................: 21 MB   694 kB/s
     data_sent......................: 8.3 MB  276 kB/s
     http_req_blocked...............: avg=1.43µs   min=882ns    med=1.22µs   max=223.79µs p(90)=1.91µs   p(95)=2.09µs  
     http_req_connecting............: avg=1ns      min=0s       med=0s       max=150.79µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=226.4µs  min=173.33µs med=215.47µs max=8.24ms   p(90)=243.94µs p(95)=255.12µs
       { expected_response:true }...: avg=226.4µs  min=173.33µs med=215.47µs max=8.24ms   p(90)=243.94µs p(95)=255.12µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 103586
     http_req_receiving.............: avg=25.41µs  min=13.73µs  med=23.67µs  max=2.51ms   p(90)=30.96µs  p(95)=33.71µs 
     http_req_sending...............: avg=6.41µs   min=4.07µs   med=5.61µs   max=970.61µs p(90)=8.2µs    p(95)=9.01µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=194.56µs min=148.52µs med=183.73µs max=8.16ms   p(90)=209.07µs p(95)=219.44µs
     http_reqs......................: 103586  3452.596655/s
     iteration_duration.............: avg=285.11µs min=216.09µs med=273.49µs max=8.34ms   p(90)=305.39µs p(95)=319.22µs
     iterations.....................: 103586  3452.596655/s
     vus............................: 0       min=0         max=1   
     vus_max........................: 1       min=1         max=1   

@renovate renovate bot merged commit 488dce3 into master Jan 30, 2025
25 checks passed
@renovate renovate bot deleted the renovate/pulumi-azure-native-2.x branch January 30, 2025 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants