Fabric resource. Default Easy Fabric and support other templates using template_props

[jgomezve]

No description provided.

[jgomezve]

This resources creates a Fabric on the NDFC/DCNM.

By default, it creates a fabric using the Easy_Fabric template. The values given in the resource are used to build the JSON payload (NV pairs) of the Easy_Fabric tempalte. Should another template be used, then values in template_props must be used to build the NV pairs. (See the example)

The resource only exposes the required arguments in addition to some arguments that I need to configure for a CX engagement. Nonetheless, the current version on the NDFC API requires all the items of the NV Pairs to be defined in the JSON payload, otherwise an alarm in raised in the NDFC GUI. As a result The models/fabric.go package automatically sets the default values int he method SetConfigDefaults().

[jgomezve]

Fix #113

[lhercot]

The dcnm go client part need to be first added to the go client itself via a separate PR to this repo: https://github.com/ciscoecosystem/dcnm-go-client

[jgomezve]

@lhercot Why are we then keeping a "copy" of that repo in this repo? Or am I missing something?

[lhercot]

@lhercot Why are we then keeping a "copy" of that repo in this repo? Or am I missing something?

Hi Jorge, we keep a copy of the code in the vendor directory in case the referenced dependency would disappear and would render it impossible for us to rebuild the provider. This is a common Golang practice referred to as "vendoring".