No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi everyone,
We are trying to use the Pulumi Splunk provider to setup indexes on the Splunk Cloud instance. Pulumi is able to create the index successfully however we aren’t able to view them in the Splunk Cloud UI. We reached out the Splunk support and they recommended to use the Splunk <https://docs.splunk.com/Documentation/SplunkCloud/9.1.2312/Config/ACSIntro|ACS> (Admin Config Service) to manage the indexes and other resources. Noticed that the Splunk ACS uses a different REST endpoint (i.e.  `<https://admin.splunk.com/&lt;stack-name&gt;/adminconfig/v2/indexes`>) compared to what Pulumi uses (i.e. `https://&lt;stack-name&gt;.<http://splunkcloud.com:8089/servicesNS/`|splunkcloud.com:8089/servicesNS/`>).
I wasn’t able to find any option in the Pulumi docs to make Pulumi to use the ACS endpoints. Can I safely assume that ACS based config isn’t supported on the Pulumi provider at this stage or I’m overlooking something. This is a blocker for us to setup the Splunk IaaC therefore any response would be highly appreciated. Thanks once again.

<https://registry.terraform.io/providers/splunk/scp/latest/docs>

^ would need a pulumi wrapper on top of this new TF provider