Resource "nxos_save_config" not working [BUG]

[krzysztofmaciejewskiit]

Version: 0.5.7

I want to save the configuration of the device with Terraform.

Logs when creating the resource that should be responsible for this.

The result on the device, which suggests an unsaved configuration. After saving manually, WARNING does not appear.

However, when I do this with the "nxos_rest" resource it saves after the second run of Terraform (it doesn't after the first - not sure why, but at least it works). The content of the resource "nxos_rest" "save" is literally a rewritten request by the API, which you can see in the debug.

API request:

[krzysztofmaciejewskiit]

From the perspective of the switch, about running the"debug nxapi-server logs" command, you can see that something interrupts the save.

[krzysztofmaciejewskiit]

@danischm are you able to help me? There is one more issue related to my case on GitHub.

[danischm]

In v0.5.8 the resource is using the JSON-RPC API to issue a "copy run start" command. Please let me know if that fixes the issue.

[krzysztofmaciejewskiit]

@danischm

• I understand correctly that we use JSON-RPC API when we use defined resources? From the Nexus perspective, commands are executed from the CLI?
• When, on the other hand, we use a generic API then we modify the DME / MO directly? What specific API is used then? Is it NXAPI? Does it also use JSON?
• Does Nexus also operate on XML?
  I looked for these things on the Internet but they are hard to find, I only found information that older Nexus use XML and newer Nexus use XML and JSON.

Can I ask for an answer to my doubts?

By the way, thanks for making the new version available right away, which should fix this, I didn't expect it.

[danischm]

NX-OS has a plethora of APIs. This config guide (https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/105x/programmability/cisco-nexus-9000-series-nx-os-programmability-guide-105x.html) provides a good overview.

• NX-API CLI using JSON or XML
• NX-API JSON-RPC
• NX-API REST
• RESTCONF
• NETCONF
• gRPC/gNMI

This Terraform provider is using the NX-API REST which interfaces with the DME object model (using JSON payloads). This is also what I have been using for the initial implementation of the nxos_save_config resource (https://developer.cisco.com/docs/nx-os-n3k-n9k-api-ref-7-x/copy-running-config-startup-config/#copy-running-config-startup-config), though apparently it wasn't always working as expected. For this single resource I have now switched to the JSON-RPC API which allows sending CLI commands to the device.

[krzysztofmaciejewskiit]

@danischm

Thanks for the links, I will definitely read them.
Do I understand correctly that different resources can use different APIs?
How do I find out which API a resource uses?

I would like to know when I am using which API when executing my Terraforms:

• NX-API CLI using JSON or XML (how to know if it communicates via JSON or XML)
• NX-API JSON-RPC
• NX-API REST

I thought maybe this example code would talk about it, but as I see it it's more like all resources have .json.

[danischm]

All resources are using the NX-API REST (using JSON). The only exception is the nxos_save_config resource which is now using the NX-API JSON-RPC.

[danischm]

You can enable TF logging (export TF_LOG=Trace) to see all API calls and payloads.

[krzysztofmaciejewskiit]

@danischm

I tested version 0.5.8.

On first run, it did not save the changes. When I did a re-run, it had already saved the changes. However, during various modifications, half the time it works the first time... So I would not say that the problem is solved.

First run:

Second run: