Add support for the Splunk Cloud Admin Config Service (ACS) API

[JosephHobbs]

Splunk Cloud has recently announced/released new capabilities to the ACS API. It would be great if these were available via this Terraform provider!

• Configure IP allow lists
• Configure outbound ports
• Manage HTTP Event Collector tokens
• Manage indexes
• Manage private apps

More information is available at https://docs.splunk.com/Documentation/SplunkCloud/8.2.2109/Config/ACSREF

Thank you!

[micahkemp-splunk]

ACS may justify having its own Terraform provider, as it uses a different service than vanilla splunkd, which is what this provider uses.

[JosephHobbs]

To be honest, I was thinking the same thing...

[pabbyt]

Do we know if this is something that is in the works? If not, do you think that opening a PR against this repo would be the way to go (modifying the client to work with the ACS API as well), or creating a wholly new provider.

[mausam-patel]

We are excited to announce the first release of the Terraform Provider for Splunk Cloud to allow automated, scalable configuration management for multiple Splunk Cloud deployments, hybrid use cases, and other services (such as AWS). The provider interacts with ACS API endpoints and currently supports the Indexes resource for both Classic and Victoria experiences.

Documentation for resources supported by the provider, as well as troubleshooting and tips, can be found here and in the Github Repo. As this is an iterative project, we request that you submit feature requests in the Splunk Ideas portal under Enterprise Cloud, and report any issues with the provider on our repo in Github. We will continue to add support for new resources, as well as update existing resources to work towards a mature, stable provider for Splunk Cloud Platform.