Allow to remap key name when mirroring secret#475
Allow to remap key name when mirroring secret#475sbenoistmics wants to merge 1 commit intoemberstack:mainfrom
Conversation
|
@winromulus Hi. |
| var newResourceAnnotations = newResource.Metadata.Annotations; | ||
| foreach (var patchAnnotation in patchAnnotations) | ||
| newResourceAnnotations[patchAnnotation.Key] = patchAnnotation.Value; | ||
| newResourceAnnotations[Annotations.Reflection.MetaAutoReflects] = autoReflection.ToString(); |
There was a problem hiding this comment.
This block is needed for tracing the source. Any reason why it was deleted?
There was a problem hiding this comment.
All the affectations are already done by the foreach loop above
README.md
Outdated
| ### 2. Annotate the mirror secret or configmap | ||
|
|
||
| - Add `reflector.v1.k8s.emberstack.com/reflects: "<source namespace>/<source name>"` to the mirror object. The value of the annotation is the full name of the source object in `namespace/name` format. | ||
| - Optionally Add `reflector.v1.k8s.emberstack.com/reflects: "<source namespace>/<source name>"` to the mirror object. The value of the annotation is the full name of the source object in `namespace/name` format. |
There was a problem hiding this comment.
I think this was supposed to be the key mapping content, since it duplicates the line above.
| } | ||
|
|
||
| Dictionary<string, string> mapping = new Dictionary<string, string>(); | ||
| try { mapping = Mapping(patchAnnotations[Annotations.Reflection.KeyMapping]); } |
There was a problem hiding this comment.
Please improve the code style. This is extremely hard to read
There was a problem hiding this comment.
Not too sure of what you mean here, I assume it is just to add line breaks
sbenoistmics
force-pushed
the
feature/key-mapping
branch
from
2e66842 to
31bfc68
Compare
Use reflector.v1.k8s.emberstack.com/reflection-key-mapping and reflector.v1.k8s.emberstack.com/reflection-auto-key-mapping to do the renaming See README.md for details
| { | ||
| foreach (var (key, value) in data) | ||
| { | ||
| newData.Add(mapping.GetValueOrDefault(key, key), value); |
There was a problem hiding this comment.
mapping.GetValueOrDefault(key, key) could easily be an empty string - which is fine. But in this case you should not copy the data over.
Example: mapping 'tls.key:' would NOT copy over the private key.
Use case: I have a secret created by the cert manager and I want to copy it over to another namespace. But I only want the public key! Private key must stay with the source...since this is kind of the point of certificates :D
There was a problem hiding this comment.
Example: mapping 'tls.key:' would NOT copy over the private key.
Not necessary true, I have a use case where two signer need the same key, I want to copy the key too.
Nevertheless I understand what you mean.
Currently you cannot copy partially, the idea was to improve the functionality, not necessary to add a comprehensive behaviour.
To do something more complex (i.e. what you suggest), a combination reflector + external-secret can do the job at the moment (technically even what I added, but it can be useful for small problems).
|
Automatically marked as stale due to no recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Automatically marked as stale due to no recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Automatically closed stale item. |
3 participants
Use reflector.v1.k8s.emberstack.com/reflection-key-mapping and reflector.v1.k8s.emberstack.com/reflection-auto-key-mapping to do the renaming
See README.md for details