Correct syntax for adding Cloud Logging Service in Automator

[dachtera]

Greetings, I need to add the cloud logging service as part of our sub-account automation, however I'm having difficulty with the syntax, and not readily seeing another example. 2 Quesions,

1. Is there a document that lists all possibly syntax/scenarios within the Automator?

2. Here is what I am using for the syntax within my json file (with assistance from the automator messages:

  {
            "name": "cloud-logging",
            "plan": "standard",
            "category": "SERVICE",
            "parameters": {"amount": 1}
             }   

This is the advice from the automator process:

[2022-10-18 14:48:52] INFO       : Assign entitlement for >cloud-logging< and plan >standard<
[2022-10-18 14:48:52] RUN COMMAND: btp --format json assign accounts/entitlement     --to-subaccount '07f9e26d-ed9d-44e8-bcb4-8d19c9da3aaa'     --for-service 'cloud-logging'     --plan 'standard' --distribute --enable
[2022-10-18 14:48:54] WARNING    : this entitlement wasn't sucesssfull. Trying to entitle with amount parameter instead.
[2022-10-18 14:48:54] INFO       : Try again to assign entitlement for >cloud-logging< and plan >standard< with amount parameter set to 1.
[2022-10-18 14:48:54] RUN COMMAND: btp --format json assign accounts/entitlement     --to-subaccount '07f9e26d-ed9d-44e8-bcb4-8d19c9da3aaa'     --for-service 'cloud-logging'     --plan 'standard' --auto-distribute-amount 1 --amount 1

This is the error message generated after the above suggested options:

[2022-10-18 14:49:53] INFO       : Create instance >cloud-logging-standard-instance< for service >cloud-logging< and plan >standard<
[2022-10-18 14:49:53] RUN COMMAND: cf create-service 'cloud-logging' 'standard' 'cloud-logging-standard-instance' -c '{"amount": 1}'
[2022-10-18 14:49:58] ERROR      : Creating service instance cloud-logging-standard-instance in org cf-dev-69434341-cb97-4d44-ad44-c44f4ab00e7c / space dev as [email protected]...

FAILED

[2022-10-18 14:49:58] ERROR      : Job (5d197dfb-fa7a-4c94-8ffc-14eb10473239) failed: An unknown error occurred.

Please advise where I have gone wrong, or if this is an issue with the latest docker image.

Thank you.

[dachtera]

This may be a non-issue as it appears to be a defaulted item when created a sub-account inheriting our global account settings. This can be closed.

[lechnerc77]

Hi @dachtera ,

ad 1) All available documentation incl. FAQs is part of the repository. There is no documentation for any combination of parameters, but the JSON schemas should help you with the right parameters. I agree that we have room for improvement there

ad 2) The btp setup automator as is supports external customer facing services as available in a PAYG account. The Cloud Logging Service s an SAP internal service, so no official support for that.
However, I did not find any edge cases for this service, so basically it should work (but no type-ahead support in the usecase.json)
According to the internal documentation of the service, the parameter you provide are wrong. You do not need to provide any parameters if the default is fine, so the usecase file should look like this:

 {
      "name": "cloud-logging",
      "plan": "standard",
      "category": "SERVICE"
  }   

You can ignore the warning when the entitlements are created. That's okay.

[dachtera]

Thank you. I tried once and got a fatal error, the second time the fatal error was not present, but resulted in a looping of attempts to move forward.

[2022-10-19 14:14:25] INFO       : check status of app subscriptions
[2022-10-19 14:14:25] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:14:33] RUN COMMAND: cf services
[2022-10-19 14:14:34] INFO       : check status of app subscriptions
[2022-10-19 14:14:34] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:14:41] RUN COMMAND: cf services
[2022-10-19 14:14:43] INFO       : check status of app subscriptions
[2022-10-19 14:14:43] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:14:50] RUN COMMAND: cf services
[2022-10-19 14:14:52] INFO       : check status of app subscriptions
[2022-10-19 14:14:52] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:14:59] RUN COMMAND: cf services
[2022-10-19 14:15:00] INFO       : check status of app subscriptions
[2022-10-19 14:15:00] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:08] RUN COMMAND: cf services
[2022-10-19 14:15:10] INFO       : check status of app subscriptions
[2022-10-19 14:15:10] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:17] RUN COMMAND: cf services
[2022-10-19 14:15:18] INFO       : check status of app subscriptions
[2022-10-19 14:15:18] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:25] RUN COMMAND: cf services
[2022-10-19 14:15:27] INFO       : check status of app subscriptions
[2022-10-19 14:15:27] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:34] RUN COMMAND: cf services
[2022-10-19 14:15:35] INFO       : check status of app subscriptions
[2022-10-19 14:15:35] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:42] RUN COMMAND: cf services
[2022-10-19 14:15:44] INFO       : check status of app subscriptions
[2022-10-19 14:15:44] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'
[2022-10-19 14:15:51] RUN COMMAND: cf services
[2022-10-19 14:15:53] INFO       : check status of app subscriptions
[2022-10-19 14:15:53] RUN COMMAND: btp --format json list accounts/subscription --subaccount 'b0ee4334-89f3-4c43-8082-e53de92e937f'

[lechnerc77]

The looping is okay, the btp-setup-automator waits until all service instances and applications are available. In the enhancement I merged today, the logging output is more expressive, what is happening than in the version you are using.
I guess the Cloud Logging Service needs some time to be up and running, which is reflected in this output.
The fatal error sounds like a temporal hickup - saw that a couple of times over the past days unfortunately, but that was related to BTP, not the automator.

[dachtera]

We may have a larger issue here as well to keep an eye on. After spinning for 10 minutes, the following error returned:

[2022-10-19 15:27:19] RUN COMMAND: cf services
[2022-10-19 15:27:20] INFO       : check status of app subscriptions
[2022-10-19 15:27:20] RUN COMMAND: btp --format json list accounts/subscription --subaccount '43fce21c-87e8-437a-b848-107489f507e0'
[2022-10-19 15:27:22] ERROR      : 
[2022-10-19 15:27:22] ERROR      : {
  "error": "500 Internal Server Error: \"{\"error\":{\"code\":10001,\"message\":\"Internal communication error\",\"target\":\"/saas-manager/v1/applications\",\"correlationID\":\"2732ac21-9995-463f-ad4e-a8ae8a2d3526\"}}\" [Error: 400]"
}

FAILED

Running a second time (without removing any existing configuration) the process completed successfully

[lechnerc77]

That's a 500 from server side - nothing where the setup automator can help imho.
Please check internally if there are issues with Cloud Logging. Maybe the polling intervals need to be adjusted, but not sure if this would fix. Also wierd that the provisioning of a logging service takes > than 10 minutes tbh.
As mentioned before it is an internal service and not in our test scope.