[ISSUE] Please list on TF provider and PVA version compatibility matrix

[pdubas]

Please provide a compatibility matrix for TF providers and private virtual appliance versions. e.g. TF provider 1.0.37 is compatible with Private Virtual Appliance 1.0.9-590

[vvb]

The providers are written to be backward compatible. So, you can use the latest provider and that should work with the appliance as well.

[pdubas]

i had to roll back to 1.0.37 I received error when grabbing the org: error occurred while fetching count of OrganizationOrganization: undefined response type Response from endpoint: {"code":"NotFound","message":"Invalid HTTP method or URL. The URL path '/api/v1/organization/Organizations?%24count=true\u0026%24filter=%28Name+eq+%27default%27%29' does not exist, or the HTTP method 'GET' is not supported for this URL.","messageId":"barcelona_invalid_http_request","messageParams":{"1":"/api/v1/organization/Organizations?%24count=true\u0026%24filter=%28Name+eq+%27default%27%29","2":"GET"},"traceId":""} I also received errors on the bios: The property 'bios.Policy:PrmrrSize' does not exist Cheers Paul Dubas 613.725.4431

…

On Thu, Oct 26, 2023 at 3:09 AM Vikrant Balyan ***@***.***> wrote: The providers are written to be backward compatible. So, you can use the latest provider and that should work with the appliance as well. — Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTHPSSBFEEKPLW3QANY2F3YBIECHAVCNFSM6AAAAAA6P3RVBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBQGUZTMNZTHA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[scotttyso]

@vvb, this isn't necessarily true for new attributes.

I just tested v1.0.44 today with a CVA and received backward compatibility issue with the new QnQ attributes for fabric_eth_network_group_policy under vlan_settings and needed to roll back to 1.0.42.

I am not sure the CVA/PVA version is the right thing to do here though. I think that the API version should be documented with the provider version release though. Because then we can go back to the API release version at least and understand what release included new versions.

Right now there isn't really any good release note that says what the new capabilities are in a provider version, which would at a minimum be a good way to know what should/shouldn't work with each provider version.

But at a minimum we need something like: provider 1.0.44 supports up to Intersight API release 1.0.11-14828

There is no direct correlation

[scotttyso]

@pdubas - The only way that you can track this is in comparing the API version with the release notes
https://github.com/CiscoDevNet/terraform-provider-intersight/releases
From the release notes you can see the version of the API supported by the released version.
Then you need to go to the CVA/PVA and look at the API version from the API Browser and choose the release that corresponds to what you need.

[druesendieb]

Came here looking for something like this. Our PVA 1.0.9-67, wouldn't work with 1.0.50 but our last tested version 1.0.45 works properly when configuring bios policies.