-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate jet-aws #219 security bug #52
Comments
This also appears to be an issue in
|
The solution should fix it for all for all OPs. So to be fixed in Upjet & Terrajet. |
I am investigating this issue. Thank you @donovanmuller for your example in Now, I realized that we have not any filtering mechanism while dumping the debug logs: So, we see all credentials of providers in logs. I think, we need a filtering process before printing these debug logs. I want to suggest two solutions and I want to hear your ideas. Firstly I want to share an example main.tf.json (as references) that is dumped in logs.
Today I want to open a PR that implements the first approach. Let's discuss here or PR! |
What happened?
crossplane-contrib/provider-jet-aws#219 is opened in upstream and we need to know whether that bug exists in Upjet as well.
How can we reproduce it?
Try to reproduce the bug for that specific resource and if it exists, fix it ASAP.
The text was updated successfully, but these errors were encountered: