Michael Tewoldemedhin
Michael Tewoldemedhin
Currently in ACK, references (policyRefs) are resolved into ARNs and stored in Spec.Policies. This makes it easier to compare them with the ARNs in AWS, and make an update. https://github.com/aws-controllers-k8s/iam-controller/blob/52217f7d94523811dd2a698089381ef7187cd54f/pkg/resource/role/references.go#L203-L207...
Hey @gecube turns out, to delete an IAM user someone needs to do the following: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_remove.html#id_users_deleting_cli This can be doable, maybe by setting an annotation deciding whether or not to...
/remove-lifecycle stale
Hello @Amir-Ahmad Thank you for bringing up this issue. SecretsManager's Secret resource does not have a conventional way of recreating the ARN from the resource name (sample secret ARN: arn:aws:secretsmanager:us-west-2:1234568279432433:secret:my-secret-4z40OU,...
>I worry about having to make a bazillion API requests just to adopt one resource, especially when dealing with pagination and accounts that have many resources. If one tries to...
Hello @Amir-Ahmad @nerdfacerory, This fix should now be available in https://github.com/aws-controllers-k8s/secretsmanager-controller/releases/tag/v1.0.13 Feel free to reopen issue if it's not yet resolved for you! /close
Hello! Thank you for taking initiative to contribute. To allow resource references please follow the following steps: https://aws-controllers-k8s.github.io/community/docs/contributor-docs/code-generator-config/#references-making-a-field-refer-to-another-resource Feel free to reach out with any questions :)
/remove-lifecycle rotten
The following PR should solve this issue: https://github.com/aws-controllers-k8s/code-generator/pull/606 /close