-
Notifications
You must be signed in to change notification settings - Fork 49
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
adding AWS Glue Job actions to test policies #95
Conversation
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.
Tested this on our staging environment with community.aws/pull/57, couple of small things here and one note I'll leave on that PR. Thanks for this!
@cdschneider The changes you have here are good, however the merge conflict is a bit hairy, partially because of #97 and partially I think from the merge commit. If you don't mind me pushing to your branch I can try to get those sorted out in the next few days. |
I don't mind at all! @jillr |
@jillr Merge looks to have gone a little wonky (@cdschneider sorry, #97 was pretty major surgery, but should massively simplify updating the policies) |
@cdschneider Sorry for the late reply, however you prefer to resolve the merge conflict works for me. |
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.
Hi @cdschneider, the policies look good but we'll also need a new class added to the terminator lambda for Glue Jobs. The terminator is a lambda function that runs in our CI account and deletes resources that have been online for longer than a set time, in case a CI job fails to clean up after itself for some reason.
You can see an example of the class for cleaning up glue connections here:
https://github.com/mattclay/aws-terminator/blob/master/aws/terminator/data_services.py#L54-L72
ETA: my apologies, I have too many tabs open - this comment was for 137!
OK @jillr I think that I've addressed all your previous comments, fixed outstanding merge conflicts, and added the |
Looking at the policies added in this PR the Glue actions look they were added in #137 and we should be able to close this PR out. |
I think tremble is right, community.aws #57 needs a rebase because we no longer use shippable (JFrog discontinued the service) and the PR needs to pick up the new CI config from |
per @tremble comments on PR ansible-collections/community.aws#57
Adding
glue:
permissions to test policies in order to support newaws_glue_job
module coverage in integration tests.