-
Notifications
You must be signed in to change notification settings - Fork 48
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(secure-onboarding) Adding AccountComponent Resource #504
Conversation
Change summary: ---------------- - Adding new Account Component resource with schema and CRUD operations in parity with Cloudauth Account resource. - Adding the respective client and support for new resource type. - Refactored common parsing methods for conversion from/to component metadata. - Added TF ACC tests for the new resource type.
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.
I think this largely looks good. I understand there are some functional cases that need to be addressed, but largely, this approach seems sound. Leaving a ✅ here even though it's likely more changes will come (and a rebase is needed).
declare common schemas used across resources here | ||
*/ | ||
var ( | ||
accountComponents = &schema.Resource{ |
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.
nit: should this be singular?
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.
actually yes, singular makes sense for SchemaComponent usage in both account and component resources. I'll fix this when I touch this part of code again.
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.
looks great @ravinadhruve10
Change summary: