Skip to content
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

aws - type metadata fixes #6314

Merged
merged 15 commits into from Dec 9, 2020
Merged

Conversation

kapilt
Copy link
Collaborator

@kapilt kapilt commented Nov 26, 2020

couple of assorted fixes

  • resource type metadata on several resources was incorrect, specifically around id
  • moves the parse_date functionality from value filter into utils
  • fixes for rds and rds cluster config source which needed unmangling of keys with DB prefixes
  • s3 logging accounts for redshift needed updating for cross-account filter

@kapilt
Copy link
Collaborator Author

kapilt commented Dec 1, 2020

hmm.. the implicit conversion on epoch time needs a guard rail, like integer value must be a date that represents an epoch value after some minimum date floor, else we're getting implicit conversion on timeouts values.

@kapilt kapilt marked this pull request as ready for review December 3, 2020 11:37
c7n/query.py Show resolved Hide resolved
@kapilt kapilt force-pushed the aws/type-fixes branch 3 times, most recently from becbd00 to 716099c Compare December 9, 2020 16:01
@kapilt
Copy link
Collaborator Author

kapilt commented Dec 9, 2020

not sure what's going on with codecov

@kapilt kapilt merged commit 808a24f into cloud-custodian:master Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant