bugfix/CSTACKEX-135: added Netapp ontap screen during zone creation

[piyush5netapp]

Description

This PR...

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

[Copilot]

Pull request overview

Adds NetApp ONTAP as a supported primary storage provider in the zone creation wizard flow, wiring UI fields through to the storage pool creation API parameters.

Changes:

• Extend zone wizard primary storage step to display NetApp ONTAP-specific fields (IP, credentials, SVM) and constrain protocol choices to NFS3/ISCSI.
• Populate createStoragePool parameters for NetApp ONTAP during zone launch, including an ONTAP-specific URL builder.
• Introduce an optional “number-format” validator hook in the shared StaticInputsForm.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
ui/src/views/infra/zone/ZoneWizardLaunchZone.vue	Adds NetApp ONTAP-specific parameter mapping and ontapURL() helper during primary storage creation.
ui/src/views/infra/zone/ZoneWizardAddResources.vue	Adds NetApp ONTAP UI fields and protocol options; hides capacity IOPS/URL fields for this provider.
ui/src/views/infra/zone/StaticInputsForm.vue	Adds optional numeric-format validation support via field.number.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new field.number validation looks unused: a repo-wide search shows no field definitions passing number: true, so this validator and rule branch won’t run for any current forms. Either add number: true to the relevant numeric/string-numeric fields (e.g., capacity fields) or remove this to avoid carrying dead code.

Suggested change

	if (field.number) {
	this.rules[field.key].push({
	validator: this.checkNumberFormat,
	message: this.$t('message.error.number')
	})
	}

[suryag1201]

could u please add screen shot or have a live demo for these UI changes?

[piyush5netapp]

could u please add screen shot or have a live demo for these UI changes?