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

Refactor SQS Resource Type #517

Merged
merged 1 commit into from
Jul 26, 2023
Merged

Refactor SQS Resource Type #517

merged 1 commit into from
Jul 26, 2023

Conversation

james03160927
Copy link
Contributor

Description

Part of #494.

TODOs

Read the Gruntwork contribution guidelines.

  • Update the docs.
  • Run the relevant tests successfully, including pre-commit checks.
  • Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
  • Include release notes. If this PR is backward incompatible, include a migration guide.
  • Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added / Removed / Updated [X].

Updated [Refactor SQS Resource Type]

Migration Guide

func getAllSqsQueue(session *session.Session, region string, excludeAfter time.Time) ([]*string, error) {
svc := sqs.New(session)

func (sq SqsQueue) getAll(configObj config.Config) ([]*string, error) {
Copy link

@zachreborn zachreborn Jul 26, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have what might be a nitpick here, the shortening of SQS Queue to sq instead of sqs. I get why, because it's similar to your other shorthand naming conventions but this one feels a bit too short for one letter difference. Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One caveat is it conflicts with the import of aws sqs library. I agree that it's more readable if we name is sqs but just to avoid conflicts with the import, sq might work better here.

@james03160927 james03160927 merged commit 0f69d82 into master Jul 26, 2023
flichtenheld added a commit to flichtenheld/cloud-nuke that referenced this pull request Nov 7, 2023
This was broken by PR gruntwork-io#517. SQS uses Unix timestamps, so
we need to make sure to treat them as such.

Signed-off-by: Frank Lichtenheld <[email protected]>
@flichtenheld flichtenheld mentioned this pull request Nov 7, 2023
1 task
james03160927 pushed a commit that referenced this pull request Nov 12, 2023
This was broken by PR #517. SQS uses Unix timestamps, so
we need to make sure to treat them as such.

Signed-off-by: Frank Lichtenheld <[email protected]>
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.

2 participants