You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***netapp-ontap_networking_ip_interface_resource**: Include min version for metrics ([[#265](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/265)])
145
157
* Fix the documentation: snapmirror and the description of other data source and resource ([[#330](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/330)])
146
158
147
159
BUG FIXES:
160
+
148
161
***netapp-ontap_cluster_data_source**: fix on nodes to show multiple elements ([#264](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/264))
149
162
***netapp-ontap_protocols_nfs_export_policy_resource**: fix id error during the creation ([[#290](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/290)])
150
163
151
164
## 1.1.3 (2024-08-08)
152
165
153
166
BUG FIXES:
167
+
154
168
***netapp-ontap_protocols_cifs_service_resource**: fixed on attribute checking ([#250](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/250))
155
169
***netapp-ontap_protocols_cifs_share_resource** :`acls` unable to update acls ([#236](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/236))
***netapp-ontap_storage_lun_resource**, **netapp-ontap_storage_lun_data_source**, **netapp-ontap_storage_luns_data_source**: added `serial_number` option to get info in state file ([#207](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/207))
162
177
163
178
BUG FIXES:
179
+
164
180
***netapp-ontap_storage_lun_resource**, **netapp-ontap_storage_lun_data_source**, **netapp-ontap_storage_luns_data_source**: fixed `name` and `logical_unit` options as separate inputs for resource and info in state file gets added separately as well ([#215](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/215))
165
181
* added guide for changing NetApp Ontap Provider from one minor version to another.
***New Data Source:**`netapp-ontap_protocols_cifs_local_group_data_source` ([#54](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/54))
180
198
***New Data Source:**`netapp-ontap_protocols_cifs_local_groups_data_source` ([#54](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/54))
181
199
***New Data Source:**`netapp-ontap_cluster_peer_data_source` ([#50](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/50))
***netapp-ontap_protocols_nfs_export_policy_resource**: Add support for import ([#34](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/34))
224
242
***netapp-ontap_cluster_licensing_license_resource**: Add support for import ([#30](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/30))
225
243
***netapp-ontap_storage_aggregate_resource**: Add support for import ([#39](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/39))
***netapp-ontap_protocols_nfs_service**: Fixed issue with version check failing for minor versions
242
261
* netapp-ontap resource and data source documentation update ([#169](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/169))
243
262
244
-
245
263
## 1.0.3 (2023-12-05)
264
+
246
265
* netapp-ontap_name_services_dns_resource: Fixed missing ID on create ([#99](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/63))
247
266
248
267
## 1.0.2 (2023-11-17)
249
-
* 1.0.1 did not deploy correctly 1.0.2 fixes that.
250
268
269
+
* 1.0.1 did not deploy correctly 1.0.2 fixes that.
251
270
252
271
## 1.0.1 (2023-11-17)
253
272
254
273
BUG FIXES:
274
+
255
275
***netapp-ontap_name_services_dns_resource**: Fixed and Documented Import ([#63](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/63))
256
276
***netapp-ontap_cluster_data_source**, **netapp-ontap_snapmirrors_data_source**, **netapp-ontap_networking_ip_route_resource** and **netapp-ontap_sotrage_volume_resource**: Fix documentation ([#70](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/70))
257
277
***netapp-ontap_name_services_ldap_resource**: Fixed and Document with the version check and workflow ([#163](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/163))
258
278
259
-
260
279
## 1.0.0 (2023-11-06)
261
280
262
281
FEATURES:
282
+
263
283
***New Data Source:**`netapp-ontap_cluster_data_source`
264
284
***New Data Source:**`netapp-ontap_cluster_licensing_license_data_source`
265
285
***New Data Source:**`netapp-ontap_cluster_licensing_licenses_data_source`
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-7Lines changed: 12 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,34 +1,39 @@
1
1
# Contributing
2
-
Thank you for your interest in contributing to the Terraform Provider for ONTAP! 🎉
2
+
3
+
Thank you for your interest in contributing to the Terraform Provider for ONTAP! 🎉
3
4
4
5
We appreciate that you want to take the time to contribute! Please follow these steps before submitting your PR.
5
6
6
7
# Creating a Pull Request
8
+
7
9
1. Please search [existing issues](https://github.com/NetApp/terraform-provider-netapp-ontap/issues) to determine if an issue already exists for what you intend to contribute.
8
10
2. If the issue does not exist, [create a new one](https://github.com/NetApp/terraform-provider-netapp-ontap/issues/new/choose) that explains the bug or feature request.
9
11
3. Let us know in the issue that you plan on creating a pull request for it, by selecting the option when creating an issue. This helps us to keep track of the pull request and make sure there isn't duplicate effort.
10
12
4. It's better to wait for feedback from someone on Netapp's Terraform Team development team before writing code. We don't have an SLA for our feedback, but we will do our best to respond in a timely manner (at a minimum, to give you an idea if you're on the right track and that you should proceed, or not).
11
13
5. Sign and submit [NetApp's Contributor License Agreement (CCLA)](https://netapp.tap.thinksmart.com/prod/Portal/ShowWorkFlow/AnonymousEmbed/3d2f3aa5-9161-4970-997d-e482b0b033fa). You must sign and submit the Corporate Contributor License Agreement (CCLA) in order to contribute.
12
-
* For Project name, select "Terraform Provider for ONTAP"
13
-
* For Project Website, enter "https://github.com/NetApp/terraform-provider-netapp-ontap"
14
+
15
+
* For Project name, select "Terraform Provider for ONTAP"
16
+
* For Project Website, enter "https://github.com/NetApp/terraform-provider-netapp-ontap"
14
17
6. If you've made it this far, have written the code that solves your issue, and addressed the review comments, then feel free to create your pull request.
15
18
16
19
Important: NetApp will NOT look at the PR or any of the code submitted in the PR if the CCLA is not on file with NetApp Legal.
17
20
18
21
## Requirement for new Resources/Data Sources
19
-
If your building a new Resouces or Data Source for the ONTAP we have a few requirements that need to be met before we can accept the PR.
22
+
23
+
If your building a new Resources or Data Source for the ONTAP we have a few requirements that need to be met before we can accept the PR.
24
+
20
25
* documentation in the /docs directory
21
26
* example in the /examples directory
22
27
* ACCtest in the /internal/provider directory
23
28
* we have a GitHub Self Hosted Action that will run the ACCtest on an internal ONTAP VSIM, if there is anything that need to be set up for the ACCtest to run please let us know in the PR.
24
29
* Pass all existing GitHub actions test
25
30
26
-
27
31
# Netapp's Terraform Team's Commitment
32
+
28
33
While we truly appreciate your efforts on pull requests, we cannot make any commitment for when, or if, your PR will be included in the Trident project. Here are a few reasons why:
29
-
* There are many factors involved in integrating new code into this project, including things like: support for a wide variety of NetApp backends, proper adherence to our existing and/or upcoming architecture, sufficient functional and/or scenario tests across all backends, etc. In other words, while your bug fix or feature may be perfect as a standalone patch, we must ensure that your code works and can be accomodated for in all of our use cases, configurations, backends, installer, support matrix, etc.
34
+
35
+
* There are many factors involved in integrating new code into this project, including things like: support for a wide variety of NetApp backends, proper adherence to our existing and/or upcoming architecture, sufficient functional and/or scenario tests across all backends, etc. In other words, while your bug fix or feature may be perfect as a standalone patch, we must ensure that your code works and can be accommodated for in all of our use cases, configurations, backends, installer, support matrix, etc.
30
36
* The Terraform Team must plan our resources to integrate your code into our code base and CI platform, and depending on the complexity of your PR, we may or may not have the resources available to make it happen in a timely fashion. As much as we would like to, and as much as we like to be "agile", we still have a roadmap of features that comes from Product Management. We will do our best, but it doesn't always happen quickly.
31
37
* Sometimes the PR just doesn't fit into our future plans. As stated above, we have a roadmap of things, and you don't necessarily know what's coming down the pike. It's possible that a PR you submit doesn't align with our upcoming plans, thus we won't be able to use it. It's not personal.
32
38
33
39
Thank you for considering to contribute to the Terraform Provider for ONTAP!
0 commit comments