You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Roadmap 2025/02 Use multiple excludedFieldsConfigs in the RemoteSyncer.
As the Platform Engineer of my team, I want to set multiple excludedFields ConfigMaps in my RemoteSyncer.
What to do
1. Change the specs to have a list of ConfigMaps instead of only one ConfigMap
Change the type to a list of corev1.ObjectReference.
ExcludedFieldsConfigMapRef*corev1.ObjectReference`json:"excludedFieldsConfig,omitempty" protobuf:"bytes,opt,8,name=excludedFieldsConfig"`// Ref to a ConfigMap
2. Loop over each ConfigMaps
Add a for loop before the check of each ConfigMaps.
Roadmap 2025/02 Use multiple
excludedFieldsConfigs
in theRemoteSyncer
.As the Platform Engineer of my team, I want to set multiple
excludedFields
ConfigMaps in myRemoteSyncer
.What to do
1. Change the specs to have a list of ConfigMaps instead of only one ConfigMap
Change the type to a list of
corev1.ObjectReference
.syngit/api/v1beta2/remotesyncer_types.go
Line 61 in 8442bb1
2. Loop over each ConfigMaps
Add a for loop before the check of each ConfigMaps.
syngit/internal/controller/webhook_request_checker.go
Lines 373 to 375 in 8442bb1
The concerned function is built in this issue: #47.
3. Get the values depending on the key
Search for the
excludedFields
key. If it does not exists, then add a condition to the status specifying that the key is not found for this ConfigMap.Additional context
If you have any questions, please tag @damsien.
The text was updated successfully, but these errors were encountered: