-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New Resource/Data Source: netapp_volume_quota_rule
#23042
New Resource/Data Source: netapp_volume_quota_rule
#23042
Conversation
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.
Hey @paulomarquesc, thanks for opening this PR. I've left some design change comments that should help with some of the complexity of this resource. Let me know if you have any questions
internal/services/netapp/netapp_volume_quota_rule_data_source.go
Outdated
Show resolved
Hide resolved
Hi @mbfrahry , thanks for these comments, it is all set now and ready for review. |
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.
Hey @paulomarquesc! Thanks for making those changes. I saw just a few more design things to take care of but they are pretty minor and just focus on consolidating or moving stuff around. We should be good to go after that!
internal/services/netapp/netapp_volume_quota_rule_data_source.go
Outdated
Show resolved
Hide resolved
internal/services/netapp/netapp_volume_quota_rule_data_source.go
Outdated
Show resolved
Hide resolved
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.
LGTM!
netapp_volume_quota_rule
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This PR introduces support for the Volume Quota Rules, which allows better control over volume quotas. It also had a little refactoring where all resources based on typed schemas moved to a models package.
Unit testing results:
Acceptance tests for resource results:
Acceptance tests for data source results: