domhanak commented on code in PR #625: URL: https://github.com/apache/incubator-kie-kogito-docs/pull/625#discussion_r1609973074
########## serverlessworkflow/modules/ROOT/pages/cloud/operator/referencing-resource-files.adoc: ########## @@ -56,11 +58,11 @@ spec: <1> The workflow defines an input schema <2> The workflow requires an OpenAPI specification file to make a REST invocation -For this example, you have two options. You can either create two `ConfigMaps` to have a clear separation of concerns or only one with both files. +The `Hello Service` workflow int the example offer two options. You can either create two `ConfigMaps`, each for one file, to have a clear separation of concerns or group them into one. From the operator perspective, it won't make any difference since both files will be available for the workflow application at runtime. -To make it simple, you can create only one `ConfigMap`. Given that the files are available in the current directory: +To make it simple, you can create only one `ConfigMap`. Navigate into the directory where your resources files are available and create the config map using following command: Review Comment: ```suggestion To make it simple, you can create only one `ConfigMap`. Navigate into the directory where your resource files are available and create the config map using following command: ``` ########## serverlessworkflow/modules/ROOT/pages/cloud/operator/referencing-resource-files.adoc: ########## @@ -79,15 +81,17 @@ You should have a `ConfigMap` with two data entries similar to this one: [source,yaml,subs="attributes+"] ---- kind: ConfigMap -apiVersion: v1 +apiVersion: v1w Review Comment: ```suggestion apiVersion: v1 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
