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

CL-858 Adding Athena support for data catalogs and prepared statements #23

Merged
merged 1 commit into from
Mar 29, 2024

Conversation

swhite-oreilly
Copy link

@swhite-oreilly swhite-oreilly commented Mar 26, 2024

This PR adds support for AWS athena data catalogs and prepared statements.

The test script for creating these resources can be found here

Note

These resource types show supported by cloud control, but when using the cloud control resource types to attempt to clean these resources, they failed to find user created resources in my testing.

Copy link
Member

@danarbaugh danarbaugh left a comment

Choose a reason for hiding this comment

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

I see the following log output when using https://github.com/oreillymedia/cl-cloud-user-creator/pull/263 with this branch to create resources from https://github.com/oreillymedia/cl-tf-aws/pull/41:

us-east-1 - AthenaPreparedStatement - my_prepared_statement - [StatementName: "my_prepared_statement", WorkGroup: "primary"] - triggered remove
us-east-1 - AthenaDataCatalog - athena-data-catalog - [Name: "athena-data-catalog"] - triggered remove
...
us-east-1 - AthenaPreparedStatement - my_prepared_statement - [StatementName: "my_prepared_statement", WorkGroup: "primary"] - removed
us-east-1 - AthenaDataCatalog - athena-data-catalog - [Name: "athena-data-catalog"] - removed

@danarbaugh
Copy link
Member

Note

These resource types show supported by cloud control, but when using the cloud control resource types to attempt to clean these resources, they failed to find user created resources in my testing.

The Nuke Inventory spreadsheet column for "aws-nuke namespace" still has the Cloud Control resource types for these resources. We should update them to reflect your AWS Nuke resource name.

@swhite-oreilly swhite-oreilly merged commit 89f3f5f into oreilly-main Mar 29, 2024
1 check passed
corybekk pushed a commit that referenced this pull request Nov 6, 2024
* chore: cleanup and standardize mock generation

* chore: improving docs and makefile
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