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

add config example #788

Merged
merged 3 commits into from
Dec 2, 2024
Merged

add config example #788

merged 3 commits into from
Dec 2, 2024

Conversation

james03160927
Copy link
Contributor

Description

fixes #786.

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].

Migration Guide

@@ -64,7 +64,6 @@ func getRegisteredRegionalResources() []AwsResource {
&resources.AppRunnerService{},
&resources.BackupVault{},
&resources.ManagedPrometheus{},
&resources.Grafana{},
Copy link
Contributor

Choose a reason for hiding this comment

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

can you rebase? both Grafana and ElasticCacheServerless where already merge

denis256
denis256 previously approved these changes Nov 26, 2024
Copy link

@stefan-nordcloud stefan-nordcloud left a comment

Choose a reason for hiding this comment

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

Hi all, I just saw this was approved now. Please note my comments here and here.

I don't know what happened. They were initially fixed when I made these comments and the conversation resolved, but now it seems like those commits have disappeared. Could you take a look at that before merging, please? Thanks!

@james03160927
Copy link
Contributor Author

Hi all, I just saw this was approved now. Please note my comments here and here.

I don't know what happened. They were initially fixed when I made these comments and the conversation resolved, but now it seems like those commits have disappeared. Could you take a look at that before merging, please? Thanks!

Hmm not sure what happened there but it's resolved now.

@james03160927
Copy link
Contributor Author

Hey @denis256, can you please approve the PR once again?

Copy link

@stefan-nordcloud stefan-nordcloud left a comment

Choose a reason for hiding this comment

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

For what its worth, I approve too 😉

@james03160927 james03160927 merged commit aa6a6e6 into master Dec 2, 2024
3 checks passed
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.

Please include a sample configuration file
4 participants