[FEAT] Re-defining a collection object is not possible

[mlubej]

What is the problem? Please describe.

Once the SH collection, such a byoc collection, is defined, it cannot be redefined, this can be annoying, and I was wondering if there are special reasons for this

E.g.

import numpy as np
from sentinelhub import Band, DataCollection

col = DataCollection.define_byoc('some-byoc-id')

If I later decide to define also bands and do

# update the collection
col = DataCollection.define_byoc('some-byoc-id', bands = [Band(name='B01', units=('DN'), output_types=(np.int16))])

This fails with

ValueError: Data collection name `BYOC_some-byoc-id` is already taken by another data collection

While it could just drop the old definition and redefine it with the bands. Or perhaps give some warning or something. Right now we have to restart the notebook kernel, which is annoying.

[zigaLuksic]

The issue is that we never know which collection is already online, and in those cases you really cannot and should not redefine it.

[mlubej]

The issue is that we never know which collection is already online, and in those cases you really cannot and should not redefine it.

But the official collections are already pre-defined and on collection definition a new collection is checked against existing ones, and then the new one is added. What if we never extend the enum, but always just check against the "official" ones?