@@ -228,10 +228,10 @@ If everything went ok, you should have a new CRD in your Kubernetes cluster. Run
Before designing the service in OSL, let us first create a CR of type `CAMARAaaS-QoDProvisiongAPI` to validate that the operator is behaving according to what is expected. To this end, you may use the test custom resource available at `/QoDProvisioningAPI/Operator/test-cr.yaml` . Before creating the resource, you need to update the fields: *spec.messageBroker.address*, *spec.messageBroker.port, spec.messageBroker.username, spec.messageBroker.password*, with the values that relate with your OSL instance. The default values will be the following ones:
-*spec.messageBroker.address: <your OSL address>*
-*pec.messageBroker.port*: 61613
-*spec.messageBroker.username: artemis*
-*spec.messageBroker.password: artemis*
-*spec.messageBroker.address:*<yourOSLaddress>
-*spec.messageBroker.port*: 61613
-*spec.messageBroker.username*: artemis
-*spec.messageBroker.password*: artemis
For now, you do not need to update the field serviceUnderControl.uuid. You may leave it as is.
