[Feat] API Key and custom headers as an alternative method of authorisation by andrew-sumner · Pull Request #1062 · nutanix/terraform-provider-nutanix

andrew-sumner · 2026-01-20T11:30:11Z

API Key allowed as an alternative to credentials
Custom headers (e.g. for Cloudflare) are supported
API Key and custom headers can be specified by environment variables
Logic for configuring provider for v4 APIs centralized

Closes #1057
Closes #1040

andrew-sumner · 2026-02-02T09:56:28Z

How do I get this PR reviewed?

GullapalliAkhil · 2026-02-04T07:30:28Z

+
+	// Set authentication - API key takes precedence if both are provided
+	if hasAPIKey {
+		apiClient.AddDefaultHeader("X-Ntnx-Api-Key", credentials.APIKey)


We have a specific method defined in the go sdk to set the API key. Can we use that instead of adding it in DefaultHeader?
example: apiClient.SetApiKey(credentials.APIKey)
https://developers.nutanix.com/sdk-reference?namespace=vmm&version=v4.2&language=golang

Unfortunately, SetApiKey() doesn't actually work in the current SDK (v4.2.1). All generated API methods are hardcoded to use authNames := []string{"basicAuthScheme"} (see categories_api.go:71), which
means the API key authentication code in prepareRequest() never executes. The AddDefaultHeader() approach works because default headers are applied after the authentication loop, regardless of the authNames list.

Can you refer to https://github.com/nutanix/ntnx-api-golang-clients/blob/main/vmm-go-client/api/images_api.go?? I guess SetApiKey() doesn't work for Prism Client https://github.com/nutanix/ntnx-api-golang-clients/blob/main/prism-go-client/api , rest all API client work with SetApiKey(), please cross check.

I had Claude look over that, too much code for me! It's finding reflect what I experienced, but to be fair I didn't delve deeper after it failed on nutanix_category_v2 data source, so I didn't realize that it worked for some.

Claude's summary:

After checking the upstream SDK source:

vmm-go-client: authNames := []string{"apiKeyAuthScheme", "basicAuthScheme"} — SetApiKey() works

prism-go-client: authNames := []string{"basicAuthScheme"} — SetApiKey() does not work

This is consistent across all files in prism-go-client/api (categories, tasks, domain_manager, etc.), and all other clients (networking, iam, clusters, vmm, volumes, etc.) do include "apiKeyAuthScheme".

However, AddDefaultHeader("X-Ntnx-Api-Key", ...) remains the correct approach for this provider for two reasons:

1. Prism v2 resources break with SetApiKey()

The following resources and data sources all go through prism-go-client and would fail to authenticate with API key if we switched to SetApiKey():

Resources Data Sources

nutanix_category_v2 nutanix_category_v2, nutanix_categories_v2

nutanix_pc_deploy_v2 nutanix_pc_v2, nutanix_pcs_v2

nutanix_pc_backup_target_v2 nutanix_pc_backup_target_v2, nutanix_pc_backup_targets_v2

nutanix_pc_restore_source_v2 nutanix_pc_restore_source_v2

nutanix_pc_restore_v2 nutanix_pc_restore_point_v2, nutanix_pc_restore_points_v2

nutanix_pc_registration_v2 nutanix_restorable_pcs_v2

nutanix_pc_unregistration_v2

2. v3 resources don't use the SDK at all

All v3 resources (VMs, subnets, images, projects, Karbon, NDB, Foundation, Self Service, etc.) use a
custom HTTP client with an applyAuthHeaders() method that sets the X-Ntnx-Api-Key header directly.
SetApiKey() is not applicable to these.

Since AddDefaultHeader() is applied after the authNames authentication loop it works uniformly
across all clients including Prism, making it the only approach that covers the full surface area of
the provider.

If it wasn't for the nutanix_category_v2 being affected by this, I'd definitely make the change.

I could implement calling SetApiKey like below.

if hasAPIKey { apiClient.SetApiKey(credentials.APIKey) // works for all clients except prism apiClient.AddDefaultHeader("X-Ntnx-Api-Key", credentials.APIKey) // fallback, covers prism }

Is it worth making this change, or is AddDefaultHeader is sufficient is enough for now and could be revisited when/if the SDK is updated?

@Haroon-Dweikat-Ntx tagging you for feedback as well.

@abhinavbansal29

Hi @andrew-sumner ,
This is the list of namespaces which have issue with the predefined method for setting API key:
Cluster Management
Object Storage Management
Prism
Security

So, for these we have to add a fallback workaround, we checked after calling this method that is the api key set in headers or not. If it is not set then we should use this workaround. We did the same in Ansible, this is a small snippet from Ansible code:

# Workaround as set_api_key not working as expected for clusters mgmt api if api_key: default_headers = getattr(client, "_ApiClient__default_headers", {}) if "X-ntnx-api-key" not in default_headers: client.add_default_header( header_name="X-ntnx-api-key", header_value=api_key )

@abhinavbansal29, I tried these approaches:

Call both

_ = apiClient.SetApiKey(credentials.APIKey) apiClient.AddDefaultHeader("X-Ntnx-Api-Key", credentials.APIKey)

Result: error while fetching subnets : {"message": "Invalid cookies present in the request"}

Likely cause: The difference in case between this SetApiKey and AddDefaultHeader resulted in 2 headers

Set if failed

if apiClient.SetApiKey(credentials.APIKey) != nil { // Client has no apiKeyAuthScheme; inject the header directly as a fallback. apiClient.AddDefaultHeader("X-Ntnx-Api-Key", credentials.APIKey) }

Result: error while fetching categories : Get "/api/iam/authn/v1/oidc/auth?%24filter=key+eq+%27Organisation%27...": unsupported protocol scheme ""

Likely cause: the != nil fallback to AddDefaultHeader never fires.

Call both but use same case for header as SetApiKey

_ = apiClient.SetApiKey(credentials.APIKey) apiClient.AddDefaultHeader("X-ntnx-api-key", credentials.APIKey)

Result: Worked

Conclusion

The problem with SetApiKey, is that whether the stored key is actually applied to a request is decided per-call in prepareRequest, which loops over the method-level authNames slice — and that's only known at call time, not at configuration time. There's no way to inspect it from the outside.

While Option 3 worked, it's very fragile in that if the case of the header ever changes, we get the result from Option 1.

The only approach that reliably works for all clients is AddDefaultHeader — the SDK's scheme-based injection is too inconsistent to depend on.

While I'll do whatever you want to get this PR in, my recommendation is to stick with current implementation.

We have raised this issue internally with the API team, you can keep the current approach for now. We will update once the new SDKs with the fix is available.

GullapalliAkhil · 2026-02-04T07:33:40Z

@andrew-sumner Can you please run all the tests, authentication method: api_key. This helps us to get the required confidence to take this in. + @Haroon-Dweikat-Ntx

GullapalliAkhil · 2026-02-10T05:30:55Z

@andrew-sumner This is an excellent improvement—we’d love to bring it in. If possible, could you start working on it soon so we can aim to include it in the next release?

andrew-sumner · 2026-02-10T06:56:03Z

Yep, aiming to have this out today.

andrew-sumner · 2026-02-10T09:36:55Z

@GullapalliAkhil I think the tests show the PR is fully functional, the failures are environment/permission-specific, not code issues.

Unit Tests

$env:NUTANIX_API_KEY = "***"
$env:NUTANIX_HEADER_CF_ACCESS_CLIENT_ID = "***"
$env:NUTANIX_HEADER_CF_ACCESS_CLIENT_SECRET = "***"
$env:NUTANIX_ENDPOINT = "***"
$env:NUTANIX_PORT = "443"
$env:NUTANIX_INSECURE = "true"
go test ./... -v -timeout 500m | Tee-Object -FilePath unit-test-results.txt

Summary:

failures: 1 - didn't set NOS_IMAGE_TEST_URL
skipped: 656 - didn't set TF_ACC
passed: 139

unit-test-results.txt

Acceptance Tests

As I am in a locked down mulit-tennant environment I've only run a subset of DataSource tests - this did highlight two issues that I had to fix:

TestAccPreCheck in acctest.go had to be updated to allow both api key and credential auth
A bug how provider.go useses NUTANIX_PORT environment variable to override the default value

$env:TF_ACC = "1"
$env:NUTANIX_STORAGE_CONTAINER = "0"

go test ./nutanix/services/clusters/... -v -run "DataSource" -timeout 30m 2>&1 | Tee-Object -FilePath test-results-readonly.txt
go test ./nutanix/services/clustersv2/... -v -run "DataSource" -timeout 30m 2>&1 | Tee-Object -FilePath test-results-readonly.txt -Append

Test failures are:

Permission issues
Test-specific configuration issues (missing attributes, empty results)

test-results-readonly.txt

andrew-sumner · 2026-02-14T20:55:10Z

@GullapalliAkhil Is that enough evidence or do you need more?

GullapalliAkhil · 2026-02-18T09:58:37Z

LGTM, @Haroon-Dweikat-Ntx Please take a look at this.

GullapalliAkhil · 2026-02-18T10:26:01Z

+
+	// Check authentication - either username/password OR api_key must be set
+	hasBasicAuth := os.Getenv("NUTANIX_USERNAME") != "" && os.Getenv("NUTANIX_PASSWORD") != ""
+	hasAPIKey := os.Getenv("NUTANIX_API_KEY") != ""


What if user set both username, Password and API key, what's the behaviour? Which one gets the precedence?

API key will take precedence I'm updating the code to display a warning.

GullapalliAkhil · 2026-02-18T10:28:09Z

+	}
+
+	// Set authentication - API key takes precedence if both are provided
+	if hasAPIKey {


We also need to handle a scenario where user set username, password and API key... We need to show a warning like provided username, password and API key, using API key and proceeding further

Have update the code to show an error if username or password is provided and not the other, and a warning if both username and password and api key are provided.

GullapalliAkhil · 2026-02-18T10:29:31Z

-* `NDB` : For Nutanix Database Service (NDB) related resources and data sources. 
+Going from 1.8.0-beta release of nutanix provider, fields inside provider configuration would be mandatory as per the usecase :

+* `Prism Central & Karbon` : For prism central and karbon related resources and data sources, `endpoint` is mandatory plus either (`username` and `password`) or `api_key` for authentication.


We need to make changes at README.md, contributing.md, env.example files as well... please take a look at them and do the needful.

Haroon-Dweikat-Ntx

LGTM. As @GullapalliAkhil noted, what is the expected behavior if both username/password and an API key are provided? Which credential has higher priority?

Haroon-Dweikat-Ntx · 2026-02-19T10:35:17Z

@andrew-sumner please fix the lint issues, and make sure to merge the master to get the latest changes.

Haroon-Dweikat-Ntx · 2026-02-23T09:23:24Z

Hi @andrew-sumner, can you please address this ASAP, we will take it in the next release
Thanks

GullapalliAkhil · 2026-02-24T06:28:45Z

Created: #1090, pipeline changes to support test execution using API KEY.

andrew-sumner · 2026-02-24T08:00:16Z

LGTM. As @GullapalliAkhil noted, what is the expected behavior if both username/password and an API key are provided? Which credential has higher priority?

API key will take precedence I'm updating the code to display a warning.

andrew-sumner · 2026-02-24T09:03:56Z

@andrew-sumner please fix the lint issues, and make sure to merge the master to get the latest changes.

I haven't been able to find any linting errors can you send me a link?
I have rebased from main

Haroon-Dweikat-Ntx · 2026-02-24T11:48:13Z

@andrew-sumner please fix the lint issues, and make sure to merge the master to get the latest changes.

I haven't been able to find any linting errors can you send me a link? I have rebased from main

https://github.com/nutanix/terraform-provider-nutanix/actions/runs/22343664899/job/64664520755?pr=1062

try to run the make fmt to fix it

andrew-sumner · 2026-02-24T20:52:21Z

@andrew-sumner please fix the lint issues, and make sure to merge the master to get the latest changes.

I haven't been able to find any linting errors can you send me a link? I have rebased from main

https://github.com/nutanix/terraform-provider-nutanix/actions/runs/22343664899/job/64664520755?pr=1062

try to run the make fmt to fix it

Thanks for that, fixed.

GullapalliAkhil · 2026-03-25T06:06:54Z

@andrew-sumner, honestly this is the first time we are doing this, it'll be helpful you provide the steps for us in doing it. This'll hep us in qualifying the custom headers and make the PR merge in master.

Given you won't have Cloudflare, you could run a minimal local proxy that prints received headers. I've been running mitmproxy locally against the latest version of the provider to inject the headers into any requests.

andrew-sumner · 2026-03-28T11:42:50Z

@GullapalliAkhil I've attached a small demo project - readme with instructions for settings this up, a script for the proxy that will log headers, and sample terraform.

DEMO.zip

As the proxy just logs and forwards, you don't need to use API key, you could use user/password auth. The Cloudflare headers should be ignored by Prism as you don't have a Cloudflare fronted api.

Setting this up did show a small issue where a header set both as environment variable and in terraform where both being added to the header - latest commit fixed that.

I've also rebased from main as this PR was showing a conflict.

@andrew-sumner, honestly this is the first time we are doing this, it'll be helpful you provide the steps for us in doing it. This'll hep us in qualifying the custom headers and make the PR merge in master.

andrew-sumner · 2026-03-28T11:45:46Z

@abhinavbansal29 Any chance you can approve the workflow on the ansible PR?

nutanix/nutanix.ansible#923

…risation to user credentials - Either API Key or credentials are required - Custom headers (e.g. for Cloudflare) are supported - API Key and custom headers can be specified by environment variables - Logic for configuring provider for v4 APIs centralised

…te docs

…re set Env var-derived header names (via NUTANIX_HEADER_ prefix) were stored under their canonical cased key (e.g. Cf-Access-Client-Id), while config-defined headers used the user's original casing (e.g. CF-Access-Client-Id). As these are different map keys the config value did not overwrite the env var value, causing both to be sent on every request. Fix by doing a case-insensitive delete of any existing env var entry before inserting the config value, preserving the user's intended casing exactly. Also replaces the custom toTitleCase helper with http.CanonicalHeaderKey in the env var path, and removes the now-redundant TestToTitleCase test.

abhinavbansal29

L.G.T.M.

abhinavbansal29 · 2026-03-31T06:35:40Z

@abhinavbansal29 Any chance you can approve the workflow on the ansible PR?

nutanix/nutanix.ansible#923

We are testing this in Ansible. We will get back on that.
Thank you

GullapalliAkhil · 2026-03-31T06:37:39Z

@GullapalliAkhil I've attached a small demo project - readme with instructions for settings this up, a script for the proxy that will log headers, and sample terraform.

DEMO.zip

As the proxy just logs and forwards, you don't need to use API key, you could use user/password auth. The Cloudflare headers should be ignored by Prism as you don't have a Cloudflare fronted api.

Setting this up did show a small issue where a header set both as environment variable and in terraform where both being added to the header - latest commit fixed that.

I've also rebased from main as this PR was showing a conflict.

@andrew-sumner, honestly this is the first time we are doing this, it'll be helpful you provide the steps for us in doing it. This'll hep us in qualifying the custom headers and make the PR merge in master.

Manually tested this by setting up reverse proxy. Thanks @andrew-sumner

[11:55:34.645][[::1]:53670] server connect 10.44.76.54:9440

>> OPTIONS https://10.44.76.54:9440/api/clustermgmt/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header

>> OPTIONS https://10.44.76.54:9440/api/vmm/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header

>> OPTIONS https://10.44.76.54:9440/api/vmm/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header

>> OPTIONS https://10.44.76.54:9440/api/clustermgmt/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header

>> OPTIONS https://10.44.76.54:9440/api/networking/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header

>> OPTIONS https://10.44.76.54:9440/api/prism/unversioned/info
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53665: OPTIONS https://10.44.76.54:9440/api/clustermgmt/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/clustermgmt/v4.2/config/clusters
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53665: GET https://10.44.76.54:9440/api/clustermgmt/v4.2/config/clusters
          << 200 OK 4.7k
[::1]:53668: OPTIONS https://10.44.76.54:9440/api/vmm/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/vmm/v4.2/content/images?%24filter=name+eq+%27Win2k12r2_Sysprep.qcow2%27&%24limit=1
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53666: OPTIONS https://10.44.76.54:9440/api/vmm/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/vmm/v4.2/content/images
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53668: GET https://10.44.76.54:9440/api/vmm/v4.2/content/images?%24filter=name+eq+%27Win2k12r2_Sysprep.qcow2%27&%24limit=1
          << 200 OK 577b
[::1]:53666: GET https://10.44.76.54:9440/api/vmm/v4.2/content/images
          << 200 OK 1.1k
[::1]:53670: OPTIONS https://10.44.76.54:9440/api/prism/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/prism/v4.2/config/categories
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53670: GET https://10.44.76.54:9440/api/prism/v4.2/config/categories
          << 200 OK 2.8k
[::1]:53667: OPTIONS https://10.44.76.54:9440/api/clustermgmt/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/clustermgmt/v4.2/config/storage-containers
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53669: OPTIONS https://10.44.76.54:9440/api/networking/unversioned/info
          << 200 OK 41b

>> GET https://10.44.76.54:9440/api/networking/v4.2/config/subnets
   Custom headers present:
     CF-Access-Client-Id: your-cf-access-client-id.access
     CF-Access-Client-Secret: your-cf-access-client-secret
   Custom headers NOT present: X-Ntnx-Api-Key, MY-Custom-Header, X-Env-Header
[::1]:53667: GET https://10.44.76.54:9440/api/clustermgmt/v4.2/config/storage-containers
          << 200 OK 1.3k
[::1]:53669: GET https://10.44.76.54:9440/api/networking/v4.2/config/subnets
          << 200 OK 1.0k

GullapalliAkhil · 2026-03-31T06:39:01Z

@Haroon-Dweikat-Ntx Let's merge this in to master and take this in to release branch. All our Iris.1 regressions should be run with this changes.

GullapalliAkhil · 2026-03-31T06:51:36Z

@andrew-sumner Can we fix lints asap?
@Haroon-Dweikat-Ntx Can we merge this and fix the lints ourselves? Waiting for @andrew-sumner will cause delay in our qualifications?

andrew-sumner · 2026-03-31T06:58:00Z

@andrew-sumner Can we fix lints asap?

@Haroon-Dweikat-Ntx Can we merge this and fix the lints ourselves? Waiting for @andrew-sumner will cause delay in our qualifications?

I can have a look in about 30 mins

andrew-sumner · 2026-03-31T07:31:08Z

Formatting issue fixed, workflow needs approval

andrew-sumner · 2026-03-31T09:18:36Z

Two approvals and a green PR, must be getting close😉

andrew-sumner · 2026-04-06T22:33:10Z

@Haroon-Dweikat-Ntx , @GullapalliAkhil , @abhinavbansal29

Thank you all for your support in getting this PR merged, it was much appreciated!

andrew-sumner mentioned this pull request Jan 21, 2026

ADD NUTANIX_API_TOKEN to connection means #1040

Closed

GullapalliAkhil requested review from GullapalliAkhil, Haroon-Dweikat-Ntx and abhinavbansal29 and removed request for GullapalliAkhil February 4, 2026 06:02

GullapalliAkhil reviewed Feb 4, 2026

View reviewed changes

GullapalliAkhil reviewed Feb 18, 2026

View reviewed changes

Haroon-Dweikat-Ntx added the 2.4.1 label Feb 19, 2026

Haroon-Dweikat-Ntx reviewed Feb 19, 2026

View reviewed changes

GullapalliAkhil mentioned this pull request Feb 24, 2026

add support for invoking tests using API keys #1090

Merged

andrew-sumner force-pushed the feat/issue#1057 branch from b5692f8 to f99f961 Compare February 24, 2026 08:58

Haroon-Dweikat-Ntx added this to Nutanix Terraform Provider 2.4.1 Feb 26, 2026

github-project-automation Bot moved this to Todo in Nutanix Terraform Provider 2.4.1 Feb 26, 2026

Haroon-Dweikat-Ntx moved this from Todo to In progress in Nutanix Terraform Provider 2.4.1 Feb 26, 2026

Haroon-Dweikat-Ntx moved this from In progress to In Review in Nutanix Terraform Provider 2.4.1 Feb 26, 2026

GullapalliAkhil approved these changes Mar 25, 2026

View reviewed changes

Haroon-Dweikat-Ntx mentioned this pull request Mar 26, 2026

Support API key auth V3 SDK and SelfService; fix acceptance tests for API-key-only environments #1110

Merged

andrew-sumner force-pushed the feat/issue#1057 branch from 04bc8c7 to c78b051 Compare March 30, 2026 03:28

dt-andrews added 8 commits March 30, 2026 16:34

Update TestAccPreCheck to allow basic and api key auth

96e8edc

Allow NUTANIX_PORT env var to override default port

e3f9236

Provide appropriate warnings/errors for authentication setup and upda…

9058d46

…te docs

Fix linting error

87dc1c3

Added NUTANIX_API_KEY and custom header example to .env.example

d33712c

Note restriction on api key for prism elements

e1c04ae

andrew-sumner force-pushed the feat/issue#1057 branch from c78b051 to 1c9d414 Compare March 30, 2026 03:34

abhinavbansal29 approved these changes Mar 31, 2026

View reviewed changes

Merge branch 'master' into feat/issue#1057

4572248

Run gofmt on provider.go

eb569d7

Haroon-Dweikat-Ntx merged commit c9db5ce into nutanix:master Mar 31, 2026
3 checks passed

github-project-automation Bot moved this from In Review to Done in Nutanix Terraform Provider 2.4.1 Mar 31, 2026

andrew-sumner deleted the feat/issue#1057 branch March 31, 2026 20:45

GullapalliAkhil assigned andrew-sumner Apr 15, 2026

Resources	Data Sources
nutanix_category_v2	nutanix_category_v2, nutanix_categories_v2
nutanix_pc_deploy_v2	nutanix_pc_v2, nutanix_pcs_v2
nutanix_pc_backup_target_v2	nutanix_pc_backup_target_v2, nutanix_pc_backup_targets_v2
nutanix_pc_restore_source_v2	nutanix_pc_restore_source_v2
nutanix_pc_restore_v2	nutanix_pc_restore_point_v2, nutanix_pc_restore_points_v2
nutanix_pc_registration_v2	nutanix_restorable_pcs_v2
nutanix_pc_unregistration_v2

Conversation

andrew-sumner commented Jan 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

andrew-sumner commented Feb 2, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GullapalliAkhil Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andrew-sumner Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andrew-sumner Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Conclusion

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GullapalliAkhil commented Feb 4, 2026

Uh oh!

GullapalliAkhil commented Feb 10, 2026

Uh oh!

andrew-sumner commented Feb 10, 2026

Uh oh!

andrew-sumner commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Unit Tests

Acceptance Tests

Uh oh!

andrew-sumner commented Feb 14, 2026

Uh oh!

GullapalliAkhil commented Feb 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Haroon-Dweikat-Ntx left a comment

Choose a reason for hiding this comment

Uh oh!

Haroon-Dweikat-Ntx commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Haroon-Dweikat-Ntx commented Feb 23, 2026

Uh oh!

GullapalliAkhil commented Feb 24, 2026

Uh oh!

andrew-sumner commented Feb 24, 2026

Uh oh!

andrew-sumner commented Feb 24, 2026

Uh oh!

Haroon-Dweikat-Ntx commented Feb 24, 2026

Uh oh!

andrew-sumner commented Feb 24, 2026

Uh oh!

GullapalliAkhil commented Mar 25, 2026

Uh oh!

andrew-sumner commented Mar 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

andrew-sumner commented Mar 28, 2026

andrew-sumner commented Jan 20, 2026 •

edited

Loading

GullapalliAkhil Feb 24, 2026 •

edited

Loading

andrew-sumner Feb 24, 2026 •

edited

Loading

andrew-sumner Feb 24, 2026 •

edited

Loading

andrew-sumner commented Feb 10, 2026 •

edited

Loading

Haroon-Dweikat-Ntx commented Feb 19, 2026 •

edited

Loading

andrew-sumner commented Mar 28, 2026 •

edited

Loading