Cloudflare-API
view release on metacpan or search on metacpan
lib/Cloudflare/API/Hyperdrive.pm view on Meta::CPAN
sub create_config {
my ($self, $body_hr, %opt)=@_;
die "config body must be a hash reference\n" unless ref($body_hr) eq 'HASH';
return $self->api()->request('POST',
$self->api()->account_path('hyperdrive', 'configs'), json => $body_hr, %opt);
}
sub replace_config {
my ($self, $id, $body_hr, %opt)=@_;
die "config body must be a hash reference\n" unless ref($body_hr) eq 'HASH';
return $self->api()->request('PUT',
$self->api()->account_path('hyperdrive', 'configs', $id), json => $body_hr, %opt);
}
sub update_config {
my ($self, $id, $body_hr, %opt)=@_;
die "config body must be a hash reference\n" unless ref($body_hr) eq 'HASH';
return $self->api()->request('PATCH',
$self->api()->account_path('hyperdrive', 'configs', $id), json => $body_hr, %opt);
}
sub delete_config {
my ($self, $id, %opt)=@_;
return $self->api()->request('DELETE',
$self->api()->account_path('hyperdrive', 'configs', $id), %opt);
}
__END__
=encoding utf8
=begin markdown
# Cloudflare::API::Hyperdrive #
# NAME #
Cloudflare::API::Hyperdrive - manage Hyperdrive connection configurations
# SYNOPSIS #
```perl
my $configs=$api->hyperdrive()->list_configs();
my $config=$api->hyperdrive()->get_config($config_id);
```
# DESCRIPTION #
These account-scoped REST methods manage Hyperdrive configurations for external PostgreSQL or MySQL databases. They do not run SQL. Applications query through a Worker Hyperdrive binding and a database driver. Cloudflare's origin password is write-on...
# METHODS #
* **list_configs(%query)** â List every configuration. Named filters become query parameters. The method follows all pages and returns one flat array reference; a large result set can require many requests and substantial memory.
* **list_configs_page(%query)** â Return a lazy `HTTP::API::Core::Pagination` object. Use `next()` to consume one configuration at a time.
* **list_configs_page_response(%query)** â Make one list request and return the complete decoded Cloudflare response hash, including `result_info` when supplied.
* **get_config($id, %options)** â Retrieve a configuration by ID and return its `result`.
* **create_config(\%body, %options)** â POST a Cloudflare configuration body and return its `result`.
* **replace_config($id, \%body, %options)** â PUT a replacement configuration and return its `result`.
* **update_config($id, \%body, %options)** â PATCH a configuration and return its `result`.
* **delete_config($id, %options)** â DELETE a configuration and return the endpoint's `result`, possibly `undef` for an empty body.
Non-list JSON methods accept `full_response => 1` for the complete decoded Cloudflare response. IDs are percent-encoded. Write bodies must be hash references; Cloudflare defines the accepted fields.
# ERRORS #
Missing account context, invalid bodies or IDs, HTTP and transport failures, and Cloudflare response failures cause exceptions as described in `Cloudflare::API`.
# SEE ALSO #
[Cloudflare::API](../API.pm.md)
# AUTHOR #
Andrew Speer <andrew.speer@isolutions.com.au>
# LICENSE and COPYRIGHT
This file is part of Cloudflare::API.
This software is copyright (c) 2026 by Andrew Speer <andrew.speer@isolutions.com.au>.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
Full license text is available at:
<http://dev.perl.org/licenses/>
=end markdown
=head1 NAME
Cloudflare::API::Hyperdrive - manage Hyperdrive connection configurations
=head1 SYNOPSIS
my $configs=$api->hyperdrive()->list_configs();
my $config=$api->hyperdrive()->get_config($config_id);
=head1 DESCRIPTION
These account-scoped REST methods manage Hyperdrive configurations for external PostgreSQL or MySQL databases. They do not run SQL. Applications query through a Worker Hyperdrive binding and a database driver. Cloudflare's origin password is write-on...
=head1 METHODS
=over
=item *
B<list_configs(%query)> â List every configuration. Named filters become query parameters. The method follows all pages and returns one flat array reference; a large result set can require many requests and substantial memory.
=item *
B<list_configs_page(%query)> â Return a lazy C<HTTP::API::Core::Pagination> object. Use C<next()> to consume one configuration at a time.
=item *
B<list_configs_page_response(%query)> â Make one list request and return the complete decoded Cloudflare response hash, including C<result_info> when supplied.
=item *
B<get_config($id, %options)> â Retrieve a configuration by ID and return its C<result>.
=item *
B<create_config(\%body, %options)> â POST a Cloudflare configuration body and return its C<result>.
=item *
B<replace_config($id, \%body, %options)> â PUT a replacement configuration and return its C<result>.
=item *
B<update_config($id, \%body, %options)> â PATCH a configuration and return its C<result>.
=item *
B<delete_config($id, %options)> â DELETE a configuration and return the endpoint's C<result>, possibly C<undef> for an empty body.
=back
Non-list JSON methods accept C<<< full_response => 1 >>> for the complete decoded Cloudflare response. IDs are percent-encoded. Write bodies must be hash references; Cloudflare defines the accepted fields.
=head1 ERRORS
Missing account context, invalid bodies or IDs, HTTP and transport failures, and Cloudflare response failures cause exceptions as described in C<Cloudflare::API>.
=head1 SEE ALSO
L<Cloudflare::API|Cloudflare::API>
( run in 0.928 second using v1.01-cache-2.11-cpan-3f962061493 )