If you already have configurations present, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/catalog/v3/providers_adapters' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "providers_adapters": [ { "provider": "Red Hat Marketplace", "providerCode": "rhm", "adapter": "http://localhost:5000/genericcontentserver/v1/providers/rhm", "discoverContent": true, "manageSOEnabled": true, "enableVersion": false } ] }
{ "totalCount": 1, "successCount": 1, "failedCount": 0, "reasons": [ { "statusCode": 201, "status": "Created", "messages": [ "providerCode: rhm5 successfully created with the provider: Red Hat Marketplace and adapter: http://localhost:5000/genericcontentserver/v1/providers/rhm" ], "id": null, "translateCode": "CA_8016_V3_PROVIDER_ADAPTER_CREATED", "translateParameters": [], "operation": null } ] }
If you already have configurations present, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/core/configuration/v1/configvalues' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "configurationkey": "d2ops_provider_conf_rhm", "configurationvalue": { "requiredForwardProxy": false, "gateway_config_key": "d2ops_gateway_config_rhm", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "endpoint": { "protocol": "http", "host": "cb-rhm-prov-adapter", "port": "7008" } } }
{ "configurationkey": "d2ops_provider_conf_rhm", "configurationvalue": { "requiredForwardProxy": false, "gateway_config_key": "d2ops_gateway_config_rhm", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "endpoint": { "protocol": "http", "host": "cb-rhm-prov-adapter", "port": "7008" } } }
If you already have configurations present, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/emp/common/clients' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "operation_fulfillment_rhm", "provider_code": "rhm", "applicable_for": [ { "id": "integration", "values": [ "OperationFulfillment" ] } ], "callback": { "url": "cb-rhm-prov-adapter:7008/adapter/rhm/v1/executeOperation", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "connection_protocol": "http" } }
{ "statusCode": 200, "status": "OK", "messages": [ "Successfully created subscriber operation_fulfillment_rhm" ], "translateCode": "CM_SUCCESSFULLY_CREATED_SUBSCRIBER", "translateParameters": [], "topics": [ "OperationFulfillment" ], "user": { "read_credentials": { "username": "default_namespace_operation_fulfillment_rhm_user1", "password": "6xTq9NN4oas6A7fc" }, "write_credentials": { "username": "default_namespace_operation_fulfillment_rhm_user2", "password": "s2NRizu5quGkIlQL" }, "accessall_credentials": { "username": "default_namespace_operation_fulfillment_rhm_user3", "password": "YCPNMPtCHbpjXTjl" }, "url": "amqp://rabbit1:5672?heartbeat=600&blocked_connection_timeout=300", "appname": "operation_fulfillment_rhm", "namespace": "default_namespace", "certificate": null } }
If you already have configurations present, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/emp/common/clients' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "operation_status_request_rhm", "provider_code": "rhm", "applicable_for": [ { "id": "integration", "values": [ "OperationStatus" ] } ], "callback": { "url": "cb-rhm-prov-adapter:7008/adapter/rhm/v1/statusOperation", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "connection_protocol": "http" } }
{ "statusCode": 200, "status": "OK", "messages": [ "Successfully created subscriber operation_status_request_rhm" ], "translateCode": "CM_SUCCESSFULLY_CREATED_SUBSCRIBER", "translateParameters": [], "topics": [ "OperationStatus" ], "user": { "read_credentials": { "username": "default_namespace_operation_status_request_rhm_user1", "password": "vzlaY75IyRU4T8cE" }, "write_credentials": { "username": "default_namespace_operation_status_request_rhm_user2", "password": "q4kfYGOc3yb7CiPf" }, "accessall_credentials": { "username": "default_namespace_operation_status_request_rhm_user3", "password": "6ZJ1IRQ9NJi3b405" }, "url": "amqp://rabbit1:5672?heartbeat=600&blocked_connection_timeout=300", "appname": "operation_status_request_rhm", "namespace": "default_namespace", "certificate": null } }
If the queue is already registered, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/emp/common/clients' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "provisioning_status_request_rhm", "provider_code": "rhm", "applicable_for": [ { "id": "integration", "values": [ "ProvisioningStatus" ] } ], "callback": { "url": "cb-rhm-prov-adapter:7008/adapter/rhm/v1/provision/status", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "connection_protocol": "http" } }
{ "statusCode": 200, "status": "OK", "messages": [ "Successfully created subscriber provisioning_status_request_rhm" ], "translateCode": "CM_SUCCESSFULLY_CREATED_SUBSCRIBER", "translateParameters": [], "topics": [ "ProvisioningStatus" ], "user": { "read_credentials": { "username": "default_namespace_provisioning_status_request_rhm_user1", "password": "r11IGGBOY3VNsVK0" }, "write_credentials": { "username": "default_namespace_provisioning_status_request_rhm_user2", "password": "WpiqKsY31SnihUq6" }, "accessall_credentials": { "username": "default_namespace_provisioning_status_request_rhm_user3", "password": "tEUa92VbZ8Tzyywg" }, "url": "amqp://rabbit1:5672?heartbeat=600&blocked_connection_timeout=300", "appname": "provisioning_status_request_rhm", "namespace": "default_namespace", "certificate": null } }
If the queue is already registered, you will get a 409 conflict. Otherwise, you will get a response like the following:curl --location --request POST '<host>/emp/common/clients' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "order_fulfillment_rhm", "provider_code": "rhm", "applicable_for": [ { "id": "integration", "values": [ "OrderFulfillment" ] } ], "callback": { "url": "cb-rhm-prov-adapter:7008/adapter/rhm/v1/provision", "certs": { "endpoint_ca_cer": "", "endpoint_cer": "", "endpoint_key": "" }, "connection_protocol": "http" } }
{ "statusCode": 200, "status": "OK", "messages": [ "Successfully created subscriber order_fulfillment_rhm" ], "translateCode": "CM_SUCCESSFULLY_CREATED_SUBSCRIBER", "translateParameters": [], "topics": [ "OrderFulfillment" ], "user": { "read_credentials": { "username": "default_namespace_order_fulfillment_rhm_user1", "password": "CwR6c7yzIcjXpCvr" }, "write_credentials": { "username": "default_namespace_order_fulfillment_rhm_user2", "password": "Oq665z0iHXXtZ2Ca" }, "accessall_credentials": { "username": "default_namespace_order_fulfillment_rhm_user3", "password": "jshleAltFPq63g9K" }, "url": "amqp://rabbit1:5672?heartbeat=600&blocked_connection_timeout=300", "appname": "order_fulfillment_rhm", "namespace": "default_namespace", "certificate": null } }
If you already have configurations present, you will get a 409 conflict. Otherwise, you will get a response like the following.curl --location --request POST '<host>/core/configuration/v1/configvalues' \ --header 'username: <username>' \ --header 'apikey: <apikey>' \ --header 'Content-Type: application/json' \ --data-raw '{ "configurationkey": "gcs_pullcontent_adapter_rhm", "configurationvalue": { "endpoint": "http://cb-rhm-prov-adapter:7008/adapter/rhm/v1" } }
{ "configurationkey": "gcs_pullcontent_adapter_rhm", "configurationvalue": { "endpoint": "http://cb-rhm-prov-adapter:7008/adapter/rhm/v1" } }