-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(iottwinmaker): add workspace, component type, entity, scene, syncjob #422
Conversation
New resources
Non-nukeable resources are marked as filtered. Scan with feature activated
Nuke with feature activated
|
c5b222c
to
5b5eda8
Compare
Interesting on the endpoint configuration. I'm working on AWS SDK v2 support which is going to require a bit of work around endpoints. What happens if you do not provide the endpoint configuration? How do the resources behave? I can test later, just don't have time at the moment. |
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.
@npellegrin thanks again for your contribution. If you don't mind please see my comments on the other pull request, it talks about renaming the pointers from like f
to r
and updating how the properties function works.
If you'd prefer I can push a commit to do the standardization changes instead.
I do appreciate the effort and the support! It is much appreciated.
If I do not add the endpoint, the resource is ignored and I can see the error in debug logs |
Thanks for the quick feedback! I will do the changes in both PR :) |
97fb1f8
to
d64cbf0
Compare
d64cbf0
to
4a2ec59
Compare
I fixed the endpoint issue with the same trick already in place for s3control, no need to add a specific YAML config with this resource :)
|
🎉 This PR is included in version 3.31.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Closes #421
IMPORTANT: To have the feature working, I had to give the endpoint in aws-nuke configuration. I guess it is the logic in pkg/awsutil/session.go not supporting the particular IoT TwinMaker endpoints. IoT TwinMaker have two endpoints:
The configuration to add to test this feature is: