1. Proposed title of this feature request
>> Need CLI so that actions that can be only done be central UI like integration, authentication can be done and CU can do some scripting and automation for some tasks.

2. What is the nature and description of the request?
>> Need CLI so that actions that can be only done be central UI like integration, authentication can be done and CU can do some scripting and automation for some tasks.

3. Why does the customer need this? (List the business requirements here)
>> CU is currently evaluating RHACS and they would like to know more about how to best manage RHACS configuration options in a repeatable / non-manual way.
For a bit of context, CU is currently deploying RHACS 3.69 on Openshift 4.9, using the Operator.

As an example, the product documentation on managing various aspects of the RHACS Platform configuration (such as configuring Integrations, authentication providers, roles, data retention etc) provides instructions on how to configure these things using the RHACS console.

While this is straightforward, we would like to know if there is a way of managing these aspects of RHACS using code, configuration files or some other easily repeatable procedure, so that we are able to quickly replicate our custom configuration in future deployment of RHACS or in DR scenarios (without relying on a backup/restore process).

The docs mention using the roxctl binary to perform certain tasks from the cli, which could be used to script some of the configuration. Looking at the different commands available, it's not clear if roxctl supports managing everything that can be configured from the console, for example tasks like configuring an authentication provider.
Could you please clarify if it's possible to manage RHACS configuration without using the console and, if so, what's the best way of doing it?

4. List any affected packages or components.
>> RHACS,

Additional Information: slackhttps://app.slack.com/client/T027F3GAJ/C02V3UGRZ0A/thread/C02V3UGRZ0A-1649914990.680449

As per the discussion with the team you are correct that the roxctl binary provides some configuration and admin tasks, but does not manage everything that can be configured from the UI. Currently, managing configuration and policy outside of the ACS UI requires using the API.

There are some examples of using the API to manage policies here: https://github.com/stackrox/contributions

Authentication to the API is handled with tokens, in the same way, that roxctl does. Refer the document: https://docs.openshift.com/acs/3.69/cli/getting-started-cli.html#cli-authentication_cli-getting-started