Need service and model

Need firewall service and model.

Need to implement all the endpoints in the Firewall Documentation.

• I'm submitting a ...
  [ ] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

This Changelog update allows for volumes to be searched for by name only. Update the getBlockStorageByName method to allow region to be optional, and only send region query param if region is present.

• I'm submitting a ...
  [*] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary
  This library pollutes the global/common Axios config with it's own config and then if you want to use Axios in your own project the config from this library gets inherited. What I am talking about is this. My problem is that I am downloading data from an S3 Bucket and the Authorization header that you add gets sent to S3 which returns and 400 error because of it. Also I don't want to inherit any of the axios configuration that this library uses.

Solution

Axios has a special function for this use case called axios.create which will create a new reusable instance where you can put your own headers/configs and stuff.

Anyone who has a local clone of this repo should do the following:

# Switch to the "master" branch:
$ git checkout master

# Rename it to "main":
$ git branch -m master main

# Get the latest commits (and branches!) from the remote:
$ git fetch

# Remove the existing tracking connection with "origin/master":
$ git branch --unset-upstream

# Create a new tracking connection with the new "origin/main" branch:
$ git branch -u origin/main

There is a new set of endpoints for DigitalOcean's CDN service.

https://developers.digitalocean.com/documentation/v2/#cdn-endpoints

Need to implement a CDN service.

Need the Floating IP Actions service and models.

Need to implement all the endpoints in the Floating IP Actions Documentation.

Need service and model.

• I'm submitting a ...
  [ ] bug report
  [x] feature request
  [ ] question about the decisions made in the repository
  [x] question about how to use this project

• Summary
  Hello!
  First, I'd like to say great work here, this is really amazing.

I'm new around here and I'm not sure if this is possible or not already in this project and probably I just have not seen it.

I'd like to be able to create a droplet from a snapshot reference

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

Now that Managed Databases are out of beta, this library needs to implement a ManagedDatabaseService. Here is the documentation regarding the available endpoints to implement. This should follow the same pattern as the rest of the services.

Need service and model.

Need to implement all endpoints in the Load Balancer Documentation.

Services:

• Floating IP

Models:

• Floating IP

Need to implement all the endpoints listed in the Floating IP Documentation.

I created a fork of this repo, in order to use it with Deno at tracker1/digitalocean-deno.

One of the things I did, is replace axios with fetch, the other is I cleaned up the services in order to remove the unnecessary nested promises. If you were interested adapting back for use in this repo should be relatively easy... mostly, copying the lib folder, and from there replacing the include... from '*.ts' removing the .ts file suffix. I also renamed the polyfill I made with fetch to request, so I had to rename some of the request data variables to data.

If you're open to merging these changes back in, I can create a pull request for you... the changes to fetch aren't strictly necessary, and could keep axios (changing the instance export name, and keeping the setup), alternatively could use the node-fetch module, and remove it entirely for browsers, and for node after 18.x becomes the LTS release, if you wanted to.

I'm hoping to get it configured for a publish to Denoland ... and possibly getting a browser and node build path... I notice there's only one test file in place, so will try and port those to deno test syntax. If you're at all interested in working together, I'm happy to do so... It seems you know the DO API far better than I do... I mostly just cleaned, removed some extra bits, and minor cleanup.

https://developers.digitalocean.com/documentation/v2/#billing-history

For methods that take input (e.g. attachVolumeToDroplet) make sure to validate that the right properties are provided, particularly the required ones.

• I'm submitting a ...
  [X] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary
  purgeEndpointCache issues a DELETE on the following endpoint: ${environment_1.API_BASE_URL}/cdn/endpoints/${id}.

This actually deletes that CDN endpoint. There needs to be a /cache at the end, see https://developers.digitalocean.com/documentation/v2/#purge-the-cache-for-an-existing-cdn-endpoint.

Need service and model.

• I'm submitting a ...
  [ ] bug report
  [x] feature request
  [ ] question about the decisions made in the repository
  [ ] question about how to use this project

• Summary
  Hi John! Is Kubernetes support planned? Thanks.

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
  https://developers.digitalocean.com/documentation/v2/#kubernetes