Consider having mutable attributes for containers #145

New issue

Open

opened 2024-12-26 13:17:37 +00:00 by alexvanin · 1 comment

alexvanin commented

2024-12-26 13:17:37 +00:00

Owner

Containers are immutable structures stored in container contract. However it is useful to set some tags or meta-info about container in runtime, which is not possible right now.

Describe the solution you'd like

Add API to attach and access mutable k:v attributes for container. There might be a reasonable limit for number of attributes.

Describe alternatives you've considered

Do nothing

Additional context

This can be useful to store some bucket settings in mutable container attributes. While it it takes a little bit longer to set, settings values will be much more consistent across storage network. Maybe it can be related to mutable container policies.

## Is your feature request related to a problem? Please describe. Containers are immutable structures stored in container contract. However it is useful to set some tags or meta-info about container in runtime, which is not possible right now. ## Describe the solution you'd like Add API to attach and access mutable k:v attributes for container. There might be a reasonable limit for number of attributes. ## Describe alternatives you've considered Do nothing ## Additional context This can be useful to store some bucket settings in mutable container attributes. While it it takes a little bit longer to set, settings values will be much more consistent across storage network. Maybe it can be related to mutable container policies.

🚀 1

fyrchik commented

2024-12-27 06:28:03 +00:00

Owner

policy contract is already a simple KV with some sugar.
Here you suggest adding similar code but in another contract.
I am wondering whether some generic KV contract might be useful, instead of extending already existing contracts and increasing their interface surface.

policy contract is already a simple KV with some sugar. Here you suggest adding similar code but in another contract. I am wondering whether some generic KV contract might be useful, instead of extending already existing contracts and increasing their interface surface.