Today we are updating the API with a few features that have been asked for repeatedly. The first feature is the ability to create or rebuild slices from backups.
We have also enabled the ability to destroy slices, but you must enable that ability from the SliceManager, which you may also disable at any time as well.
We've set a user-definable limit of maximum # of slices built in a day, which can be a safeguard against an accidental infinite loop.
Slices also have a number of new attributes:
We strive to make each release of the API as backwards-compatible as possible, however there is one small change you may have to make for your Slice models to work.
If you're using Ruby's ActiveResource::Base class, Slices now require an Address class. Since we include one or more IP addresses in an array, ActiveResource requires that it have it's own class. You can simply add on line though:
class Address < String; end
Since the IP addresses are nothing more than strings, this is the easiest way to use them.
Since we first unveiled the API, we have had excellent feedback and suggestions from many of our users. The first release only had support for DNS zones and records, which, as our clamoring customers let us know, was not enough!
So today, I am pleased to announce version 1.3 of the API which includes support for creating, rebooting, and rebuilding Slices. This will allow for quick and easy deployment, taking us another step in the direction of user-specified automation.
This is the first step to adding Slices to the API, which brings along several caveats:
Also note that the charges for new Slices are prorated the same as in the SliceManager.
The future of the API will is dependent on the feedback we receive; What is most important to you? Please let us know how we can improve our service, and we will do our best to make it possible.