If I have Resource Manager/ID Allocator allocated IDs from a pool, is there any way to lock those IDs so they are maintained even if an exclude statement is added that encompasses those IDs?
IE: Range is 1 to 65535, allowed range day 0 is 1 to 5000, but later I want to update allowed range to be 10000 to 65535. I could exclude any unused IDs from the day 0 range, but if any of the services in that range gets removed, I'm currently using first free allocation so those would be fair game for reassignment, and I don't want that. If I put an exclude over the whole day 0 range, it reallocates existing IDs into an available range, but this causes issues with re-deployment and/or deletion. I would prefer to have ID reuse, but the only way I'm seeing right now to avoid reassignment or use of IDs in an undesired range is to use the round robin allocation unless I can somehow lock the allocations from being changed.
