Re: [DISCUSS] KIP-1110: Metadata of sensitive configuration

Bump this thread to seek for feedback or suggestions. Thanks. Luke On Tue, Nov 26, 2024 at 4:30 PM Luke Chen wrote: > Hi Federico, > > Thanks for the comment. > I've updated the field name to LastUpdateTimestampMs. > > Luke > > On Tue, Nov 19, 2024 at 7:21 PM Federico Valeri > wrote: > >> Hi L

Re: [DISCUSS] KIP-1110: Metadata of sensitive configuration

Hi Federico, Thanks for the comment. I've updated the field name to LastUpdateTimestampMs. Luke On Tue, Nov 19, 2024 at 7:21 PM Federico Valeri wrote: > Hi Luke, thanks for creating this KIP. It makes sense to me. > > I think using timestamp in this case is fine, as the operator only > needs t

Re: [DISCUSS] KIP-1110: Metadata of sensitive configuration

Hi Luke, thanks for creating this KIP. It makes sense to me. I think using timestamp in this case is fine, as the operator only needs to know if the value changed, not when it changed (in that case clock drift could be a problem). Should we name the new DescribeConfigs field as "LastUpdateTimesta

[DISCUSS] KIP-1110: Metadata of sensitive configuration

Hi all, I've opened the KIP-1110: Metadata of sensitive configuration . Instead of returning null for sensitive configs, by returning metadata of the sensitive configs allowing the operators to hav