tree d89c2c3e210a7d5bd92a7c32012c0d59e87031d0
parent dff4708ea01929e9cdc60373d937ebbde8c705b6
author Molly Gao <31704180+mgao0@users.noreply.github.com> 1649178781 -0700
committer GitHub <noreply@github.com> 1649178781 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiTHidCRBK7hj4Ov3rIwAAN+kIACAFPuzOaz6/UAPPouNHln1P
 wlqPQtiMCWmCCNqpXYK7zlqbiVGh1kcA/nQYNeWBPGzHES/w4fyLuT3a1ajO7kkv
 VcuKtLQW8TUkBomuwV+Z2dR7wPEM/2oxKcYNVufw1GM7ljLkNHJbZNQwtcTX3Uh6
 8ppt7ZMZKjatECqCgTOG9yTg1TUeSqVilGa9GTuu991xbmJeTyN8wOZpqXJHiZyb
 XScjZxo6K+qr6SK20Q6ErpvkaoyUbWHrI5LbwMOAMIPMq2MFTxGHW+n7TWpxJ7EY
 83qRg6BBe9a8wD0aYOhtmo6SoSAGlQttPQPfxjyX0aXYup0xcWPFchrBcKMY2sA=
 =SL5b
 -----END PGP SIGNATURE-----
 

Populate helix cloud property using cloud config (#2005)

Currently when instantiating a zk helix manager, we retrieve cloud config from zk and replace entire HelixCloudProperty object, which may cause some fields that user pass in in HelixCloudProperty that are not included in cloud config get missing. This commit changes the logic to only populate fields in HelixCloudProperty with values that are present in cloud config, and leave other fields unchanged.