How do I import a configuration intent type?
Before you begin
Before you can import an intent type, the intent type must be present in the NSP with the InfrastructureConfiguration label. You can import a bundle of intent types into NSP; see “How do I install an artifact bundle?” in the NSP Network Automation Guide.
Intent types that have already been imported appear dimmed in the import form. To import changes to an intent type, perform a re-import from the Table row actions menu.
Note: The intent type must include an icm_descriptor resource file. If the resource file is missing a mandatory attribute, the import fails with the error message “Invalid descriptor file. Missing attributes” where attributes is the list of mandatory attributes that are missing from the file. See Descriptor resource file for information about the requirements for the descriptor file.
Steps
1 |
Open Device Management, Configuration Intent Types. |
2 |
|
3 |
In the form that opens, choose the intent types and click IMPORT. The list of intent types is updated. Note: The more schema form content an intent type has, the longer it takes to import. End of steps |