Latest changes for the RHOAS CLI. For information on what was included in latest release please refer to our changelog
RHOAS CLI now uses the new service account SDK to make requests for service account related operations.
The temporary flag "--enable-auth-v2" added in v0.51.0 to facilitate migrating to the new SDK has been deprecated along with usage of Control Plane SDK for service account operations.
CLI now supports a request command to perform generic api calls.
rhoas request -h
CLI now supports commands to view and modify owner of a Service Registry artifact.
rhoas service-registry artifact owner-get can be used to view the owner of the artifact.
rhoas service-registry artifact owner-set can be used to edit/set owner of an artifact.
NOTE: Only the current owner of an artifact or any user with the Admin role is allowed to change the owner.
Commands have been added to enable users to fetch state for their organization and personal account required for Kafka instance creation.
Supported commands:
rhoas kafka providers can be used to fetch valid cloud providers, regions and supported plans.
rhoas kafka billing can be used to fetch billing type, marketplace cloud provider and marketplace cloud account IDs.
CLI now supports both Control Plane SDK and the new Service Account SDK. While Control Plane SDK is still being used to make requests, user can pass "--enable-auth-v2" flag to get the data formatted according to the new Service Account SDK.
"--enable-auth-v2" is a temporary flag to facilitate users to migrate to the new SDK. The flag will be deprecated in future releases along with deprecation of using Control Plane SDK for service account operations.
Our expanded support for Red Hat OpenShift Connectors is now available for you to use. You can create a Connector instance definition file by using rhoas connector build. A definition file can be used to create one or more Connector instances using rhoas connector create
rhoas connector build can be used to create a definition file for a Connector type.
rhoas connector create can be used to create a Connector instance based on the configuration you generated with rhoas connector build.
Use the --type flag to pick which connector type you want to deploy. You can list and search through all available Connector types use the command with the --search flag:
rhoas connector type list --search=AmazonUpdating the state of a Connector instance can also be done from the CLI using the command:
rhoas connector updateYou can also create a new namespace using the command:
rhoas connector namespace createEach created Connector instances and namespaces are set in the active service context. To update your context or to remove services from the context for either a namespace or Connector instance use:
rhoas context unset --services=connector,namespaceYou are now able to interact with Red Hat OpenShift Connectors directly from the CLI. You can create a new connector by using rhoas connector build in conjunction with rhoas connector create.
Use the --type flag to pick which connector type you want to deploy. You can list and search through all availble connector types use the command with the --search flag:
rhoas connector type listYou can also create a new Connectors namespace using the command:
rhoas connector namespace createNewly created Connectors instances and Connectors namespaces are set in the current service context. To update your context or to remove services from the context for either a namespace or connector use:
rhoas context unset --services=connector,namespacerhoas service-registry setting get for getting the value of a setting for a Service Registry instance. Supports the --name flag to define the setting name.
The setting name can also be prompted by running the command in interactive mode:
rhoas service-registry setting get
rhoas service-registry setting set for configuring the value of a setting for a Service Registry instance. Supports the --name flag to define the setting name and --value to define the setting value. --default restores the default value.
The setting name and value can also be prompted by running the command in interactive mode:
rhoas service-registry setting set
rhoas service-registry setting list for listing all settings for a Service Registry instance.
NOTE: The
service-registry settingcommand is only available to Service Registry instance owners, instance administrators, and organization administrators.
Earlier versions of RHOAS CLI created service accounts and generated configuration file containing URLs to service instances and credentials for service accounts.
From this version, rhoas generate-config command will no longer create service accounts and the generated configuration file will only contain the URLs.
With config-generate command generating only URLs to the configuration file, it will be beneficial to have them generated in a ConfigMap format.
rhoas generate-config --type configmap
rhoas generate-config command no longer supports the secret output type. The credentials for service accounts can be generated in a Openshift secret file and can be used along with the ConfigMap for service instances.
rhoas kafka create now supports --billing-model flag that allow users to specify the type billing details for your kafka instance.
--billing-model along with --marketplace and --marketplace-account-id flags can be used to specify the
billing details.
Billing details can also be prompted by running the command in interactive mode:
rhoas kafka create
rhoas kafka topic produce and rhoas kafka topic consume for producing and consuming messages to a kafka topic.
New produce and consume commands work without any configuration and will point to your current Kafka instance by default.
Commands can act as alternative to kcat and kafka bin scripts by providing unified interface and simplicity of use.
NOTE: commands are released as technology preview. Some of the flags and arguments can change without any notice.
New --overwrite flag for rhoas generate-config enables users to overwrite their current configuration
RHOAS CLI would use only single SSO provided by default. Users will not longer see multiple tabs opened when login and communicate with two different authentication servers.
NOTE: This change should not affect users and it have been documented only for informational reasons
rhoas completion powershell will enable developers to get command completions on Windows platforms
NOTE: Feature have been provided by our community. We are looking for feedback on usability of Powershell extensions.
rhoas kafka create supports now --marketplace and --marketplace-account-id flags that allow users to specify AWS marketplace details for billing purposes.