-
Notifications
You must be signed in to change notification settings - Fork 1
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 937 bedrock #33
Cl 937 bedrock #33
Conversation
…group (rebuy-de#1229) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…roup across 1 directory (rebuy-de#1246) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Curious about this. If we already know the pattern, wouldn't we filter them out in this module like other modules do? |
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.
@corybekk we need to add properties functions similar to something like this as they are asking for those upstream:
func (f *CodePipelineCustomActionType) Properties() types.Properties {
properties := types.NewProperties()
properties.Set("Category", f.category)
properties.Set("Owner", f.owner)
properties.Set("Provider", f.provider)
properties.Set("Version", f.version)
return properties
}
@swhite-oreilly I thought this was optional. I am trying to find it, can you show me where it's being asked for upstream? Edit: Added them for good measure: 2e67160. Thanks for the callout.
@corybekk something is wrong with the filtering as well, when I run nuke all resources are successful except for that alias.
|
Thanks @sstoops for pointing that out! I didn't realize there was an optional filter function being used in the pattern. Ive added it 5ea0b67 and will remove the settings.py filter that is in the companion PR. here is the updated output. aws-nuke version unknown - unknown - unknown
edit: I removed the agent alias filter. It looks like we don't need it after all. 1e5142c |
@swhite-oreilly it looks like you weren't filtering out the alias. It needs to be added to config.yml. Nonetheless, as per Seans comment, I have added filtering here: 5ea0b67. You should now get this as output:
I also removed the agent alias because it looks like in your example you had no issues with it. I also tested locally and didn't see the alias pop up. I'm doing a little more research on this alias. Just to make sure we really don't need it. |
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.
@corybekk pending my question to Sean regarding the go/editorconfig changes, I think this looks good. Thanks for adding the filter, I just had the original team ask for these as part of the standard setup going forward. The filtering worked correctly as well, thanks!
@@ -0,0 +1,132 @@ | |||
# Distributed via https://github.com/rebuy-de/terraform-cluster-config |
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.
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.
Honestly, I think you've hacked on aws nuke more than I have at this point! It does look like the result of main
not having been merged over to oreilly-main
first. I'm not sure it's a big deal (especially given our entire uncertain future with aws nuke).
* docs: add note about continued attribution * chore: improve internal tooling
Description
Added the
bedrock-flowalias.go
module for deleting bedrock flow-alias resources.Added the
bedrock-agentalias.go
module for deleting bedrock agent-alias resources.Observation
Note: Attempting to cleanup these resources in aws-nuke with their cloud control resource will result in the following errors:
Testing
you can use the
bedrock.sh
from the companion PR to create the flow and agent resources. It also might be helpful to comment out the other bedrock resources in the script unless they are already included in your cleanup config.Output