Yusuke Kuoka

@maxbrunet Hey! > Reconcile K8s secrets with SecretsManager would simplify the process by removing a step. I guess no. The suggested proposal seems to update the K8s secret without recreating...

I mostly agree, but there's a pitfall. When this feature is used with `Deployment` or `CronJob`, you don't really have a control of when the changes to secrets are "applied"...

Hi! Unfortunately, it isn't possible today. Can we just extend the spec to accept two or more `secretsManagerSecretRef`s and merge them? On duplicate key, the latter and newer value for...

@sh240293 This is what it does and there's no hard limit of 10. https://github.com/mumoshu/aws-secret-operator/blob/564875e31ec98992f83252f0d4896c77b3f79343/controllers/awssecret_controller.go#L57-L115 Also, this issue was about trying to create a single K8s secret from multiple secretsmanager secrets...

@sh240293 Hey. Your error seems to be coming from https://github.com/toVersus/aws-ssm-operator, not aws-secret-operator.

@cirulls Thanks for reporting! What a coincidence - I just realized this while reviewing the manifests. Just updated it to 0.3.3 in 540830c30d9ff8f7bae76bddc802532b2afdd4fc

@james-nduka Hey! It's not supported, but technically possible. Today, we only use AWSVersionID for change detection: https://github.com/mumoshu/aws-secret-operator/search?q=AWSVersionID We may instead use another store, like some annotation on the secret resource...

Thansk! Yeah, just give AWS credentials to the pod in your preffered way. AWS_PROFILE, AWS_ACCCESS_KEY_ID/AWS_SECRET_ACCESS_KEY, kiam, kube2iam, kube-aws-iam-controller or whatever...

Thanks for reporting! Unfortunately, this has never reproduced in my own environment. If anyone can provide me successful reproduction steps, it would be more than welcome.

@hhamalai Ah! Thank you so much for pointing it out. It does seem like I have unintentionally broken the existing "undocumented" behavior. Yes, my intention was always to force providing...