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
fix: propagate preferred_maintenance_window
to the docdb cluster instances resources
#57
fix: propagate preferred_maintenance_window
to the docdb cluster instances resources
#57
Conversation
preferred_maintenance_window
to the docdb cluster instances resourcespreferred_maintenance_window
to the docdb cluster instances resources
is there like a known issue with the Github workflow? .. Seems like the workflow wants to push something to my forked repo and it fails .. |
@sherifkayad thanks for the PR Please run the following commands and commit the changes:
|
/test all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please see comments
I have rolled out the updated workflows to this repo, please rebase on main, run
and it should all be green 👍 |
preferred_maintenance_window
to the docdb cluster instances resourcespreferred_maintenance_window
to the docdb cluster instances resources
…tances resources Signed-off-by: Sherif Ayad <sherif.k.ayad@gmail.com>
@aknysh @max-lobur thanks for your comments. I rebased, ran the required commands and pushed again. Could you please have another look? |
/test all |
@aknysh is that something I can fix? .. Didn't quite get why the linting is failing |
after another check, seems like the linter is failing on all 17 occurences of |
Signed-off-by: Sherif Ayad <sherif.k.ayad@gmail.com>
@sherifkayad yes, this is the issue, thank you |
/test all |
/terratest |
propagated
preferred_maintenance_window
to the docdb cluster instances resourceswhat
aws_docdb_cluster_instance.default
such that the cluster and its instances have the same value given by the userpreferred_maintenance_window
from the variables isn't propagated to thedocdb_cluster_instance
resources #55why
references