I understand that it is not possible to create devices with legacy buckets on the Tago web interface anymore.
However, using the old API, it’s still possible to create legacy buckets and as far as I know, the old API will be supported until 2030 (reference: https://github.com/tago-io/tago-sdk-js).
Does this mean that we will still be able to use legacy buckets using the old API until 2030?
What about the new API? Will the legacy option supported using the new API until 2030?
I am asking this because legacy buckets work the best for our application - we need to modify some variables but we also actively use data retention policies… and those two unfortunately don’t mix using the new formats. So I’d like to keep using the legacy buckets until possible but also move to the latest JS API to avoid using old software… but if that won’t work in the future, we’ll have to schedule the work converting to the new bucket formats.
Also, is it possible to convert a legacy bucket to a mutable or immutable bucket with keeping the data?
1 - The buckets of the type legacy will be deprecated very soon, we’re currently migrating buckets of accounts that still use them, since users need to sometimes apply changes to their application logic. The SDK will be supported until 2030, not the legacy buckets.
I just asked our CSM team to contact you to assist you through the process.
2 - It is possible to convert the legacy buckets to the new ones. The bucket must be empty before being converted, and after the conversion, the data can be restored.
Thanks for the explanation. I think you should see an alternative for the immutable buckets and the removal of specific data. I have many devices from which I have to remove erroneous data by parsing, but this does not work with immutable buckets. So I have to use a mutable and then an immutable, which is very time consuming, plus it leaves only half of the devices in my account available. Please evaluate this, there must be several clients in the same situation, thanks.
