Feat: support tracking binaryData in CM#1929
Conversation
Signed-off-by: MengjiaLiang <mengjia.liang@uipath.com>
Signed-off-by: Arman Babaei <292arma@gmail.com>
Signed-off-by: Arman Babaei <292arma@gmail.com>
Signed-off-by: Arman Babaei <292arma@gmail.com>
|
|
||
| if ct.TrackBinaryData { | ||
| for k, v := range config.BinaryData { | ||
| data[k] = string(v) |
There was a problem hiding this comment.
using a string to store binary data is not ideal. any invalid utf-8 chars is replaced with \ufffd. this could to lead the same checksum being generated for different binary data.
go playground: https://go.dev/play/p/aK0c8PId3Nv
| enableLeaderElection bool | ||
| leaderElectionNamespace string | ||
| enableConfigTracking bool | ||
| enableConfigBinaryDataTracking bool |
There was a problem hiding this comment.
this needs to be exposed in the helm chart as well
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1929 +/- ##
==========================================
+ Coverage 30.00% 30.03% +0.03%
==========================================
Files 288 288
Lines 18455 18464 +9
==========================================
+ Hits 5537 5546 +9
Misses 12189 12189
Partials 729 729 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
3 participants
Currently, Flagger does not support creating/tracking/promoting the binaryData in a configmap.
This change tries to support these scenarios under a new feature flag
enable-config-binary-data-tracking.This resolves the comments in #1781