Closed pierluigilenoci closed 2 years ago
@kishorj @bwagner5 @rexnp @saiteja313 @M00nF1sh
Who should I ask for feedback?
@cgchinmay @shaileshgupta2k @achevuru could you please take a look?
@willtong1234 @yuriadams @LeandroFranciscato @parimaldeshmukh @StevenEmelander @joebaro @lasred @NissesSenap could you please take a look?
Most new charts published are being put into the main app repo and sync'd over, so you were correct to pursue that route. But let's put this one in eks-charts first and then we can look at moving the main copy to the app repo later with a sync process.
@bwagner5 let me know if there is anything else I can do.
Fast recap:
The PR is merged so we can close this issue.
Ref: https://github.com/aws/eks-charts/tree/master/stable/csi-secrets-store-provider-aws
Is your feature request related to a problem?
I wrote a chart to deploy csi-secrets-store-provider-aws provider and opened a PR on the project repo. Ref: https://github.com/aws/secrets-store-csi-driver-provider-aws/pull/35
It has been lying ignored for months and so I wondered where I was wrong.
Should I do the PR for the above chart in this repo?
Is your feature request related to a specific Helm chart, if yes mention name of the chart?
csi-secrets-store-provider-aws
Describe the solution you'd like
Propose a new chart
Describe alternatives you've considered
Find someone on AWS who can approve my chart in the other repo https://github.com/aws/secrets-store-csi-driver-provider-aws/pull/35