As of now, configs are not versioned, meaning we cannot retreive older states of a config.
This causes implications in the software. For example, when a stream is created with a given config, and the config is then updated, we have no way of knowing what the actual stream definition was upon creation.
If the connection information is changed to point at a different kafka cluster, we would either effectively be using a different underlying kafka topic or the topic might not exits, causing pipelines/deployments to break.
To fix this, we should introduce versioning of configs and resources should reference the config with a version number. This guarentees we always have the information used for the creation of the configured resource.
As of now, configs are not versioned, meaning we cannot retreive older states of a config. This causes implications in the software. For example, when a stream is created with a given config, and the config is then updated, we have no way of knowing what the actual stream definition was upon creation.
If the connection information is changed to point at a different kafka cluster, we would either effectively be using a different underlying kafka topic or the topic might not exits, causing pipelines/deployments to break.
To fix this, we should introduce versioning of configs and resources should reference the config with a version number. This guarentees we always have the information used for the creation of the configured resource.