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

feat(secure-onboarding) Adding AccountComponent Resource #504

Merged
merged 6 commits into from
Apr 26, 2024

Conversation

ravinadhruve10
Copy link
Contributor

@ravinadhruve10 ravinadhruve10 commented Apr 24, 2024

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.
  • Added docs md for the new resource

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.
Copy link
Contributor

@cgeers cgeers left a 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).

@ravinadhruve10 ravinadhruve10 marked this pull request as ready for review April 26, 2024 02:51
declare common schemas used across resources here
*/
var (
accountComponents = &schema.Resource{
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

@cgeers cgeers left a comment

Choose a reason for hiding this comment

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

looks great @ravinadhruve10

@cgeers cgeers merged commit b33d7dd into master Apr 26, 2024
23 checks passed
@cgeers cgeers deleted the feat/onboarding/comp-resource branch April 26, 2024 14:18
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