Depends on D8612.
overall support this direction - leaving open for feedback from others
is the schedule apis coming as a diff on top of this? curious to see how that looks
re: my favorite thing to bring up around this config, will want to communicate here some how
nit: PartitionsConfig reads a little odd to me. If users are unlikely to construct directly not sure how much it matters but throwing out some alternatives
a little unfortunate to lose this capability, seems recoverable if feedback pushes us that way
Totally. I added some warnings about putting in sensitive values. I'm a little hesitant to say "you can use a config mapping with no outer schema to set config in a not viewable way", because I think it would be valuable at some point in the future to expose these inner config values for debugging.
IMO config is just not the right place for sensitive information. Maybe worth a bigger conversation?
Yeah, me too. I changed to PartitionedConfig.
I just tried playing with this and I think it's a little awkward, because it still leaves preset out. I'm going to merge without it, but can make the change if you feel strongly.