You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* OTEL update
* Tracing update
* APISIX password update
* APISIX updates
* Sample app update
* updates for 400 auto-scaling
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
* general review and updates
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
* add soc docs
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
* Spelling, version correction, linting
---------
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
Co-authored-by: Mark Nelson <mark.x.nelson@oracle.com>
uploading: obaas/myserv/target/demo-0.0.1-SNAPSHOT.jar building and pushing image...
411
412
binding resources... successful
412
413
creating deployment and service... successfully deployed
@@ -415,7 +416,9 @@ Ask for Help
415
416
or, for native compiled microservices, add **--java-version container-registry.oracle.com/os/oraclelinux:7-slim** to have a compact image and **--graalvm-native** to specify the file provided is an executable .exec:
* Add a specific configuration using the set of parameters `--service-name`, `--service-label`, `--service-profile`, `--property-key`, and `--property-value`. For example:
@@ -997,7 +1012,7 @@ Manage users allows you to create the platform users and assign the roles that g
997
1012
998
1013
Use the `user create`command to add users to the platform. This command requires the name of the user `username` and the user roles in a comma-separated list.
999
1014
1000
-
```bash
1015
+
```text
1001
1016
oractl:>help user create
1002
1017
NAME
1003
1018
user create - Creates a new user in your platform.
@@ -1007,7 +1022,7 @@ SYNOPSIS
1007
1022
1008
1023
OPTIONS
1009
1024
--username String
1010
-
The name you assign to the user during creation. This is the user’s login forthe CLI and for the SOC UI, also. The name must be unique across all usersin the platform and cannot be changed.
1025
+
The name you assign to the user during creation. This is the user's login for the CLI and for the SOC UI, also. The name must be unique across all users in the platform and cannot be changed.
1011
1026
[Mandatory]
1012
1027
1013
1028
--roles String
@@ -1161,7 +1176,7 @@ oractl:>user list
1161
1176
1162
1177
Use the `user delete` command to remove users from the platform.
1163
1178
1164
-
>ATTENTION: Ensure that you want to completely delete the user. You cannot rollback the user profile once deleted.
1179
+
> NOTE: User deletion is permanent and irreversible.
`app.container.port` | `8080` | This sets the listen port for the pod and service. The Spring Boot application will listen on this port. The default is `8080`. This can be set using the `--port` parameter on the `deploy` command in the CLI.
14
-
`spring.profiles.active` | `default` | This sets the Spring profiles that will be active in the application. The default value is `default`. This can be changed set the `--service-profile` parameter on the `deploy` command in the CLI.
15
-
`spring.config.label` | `0.0.1` | This is a label that can be used with Spring Config to look up externalized configuration from Spring Config Server, along with the application name and the profile.
16
-
`eureka.instance.preferIpAddress` | `true` | This tells the Eureka discovery client to use the `preferIpAddress` setting. This is required in Kubernetes so that service discover will work correctly.
17
-
`eureka.instance.hostname` | `customer32.application` | This sets the hostname that Eureka will use for this application.
18
-
`MP_LRA_COORDINATOR_URL` | `http://otmm-tcs.otmm.svc.cluster.local:9000/api/v1/lra-coordinator` | This is the URL for the transaction manager which is required when using Eclipse Microprofile Long Running Actions in your application.
19
-
`MP_LRA_PARTICIPANT_URL` | `http://customer32.application.svc.cluster.local:8080` | This is the participant URL which is required when using Eclipse Microprofile Long Running Actions in your application.
20
-
`eureka.client.register-with-eureka` | `true` | This tells the Eureka discovery client to register with the Eureka server.
21
-
`eureka.client.fetch-registry` | `true` | This tells the Eureka discovery client to make a local copy of the registry by fetching it from the Eureka server.
22
-
`eureka.client.service-url.defaultZone` | `http://eureka.eureka:8761/eureka` | This is the default zone for the Eureka discovery client.
23
-
`zipkin.base-url` | `http://jaegertracing-collector.observability.svc.cluster.local:9411/api/v2/spans` | This is the URL of the Zipkin-compatible trace collector which can be used by your application to send trace data to the platform.
24
-
`otel.exporter.otlp.endpoint` | `http://open-telemetry-opentelemetry-collector.open-telemetry:4318/v1/traces` | This is the URL of the OpenTelemetry (OTLP protocol) trace collector which can be used by your application to send trace data to the platform.
25
-
`config.server.url` | `http://config-server.config-server.svc.cluster.local:8080` | This is the URL of the Spring Config Server provided by the platform.
26
-
`liquibase.datasource.username` | set to the key `db.username` in secret `admin-liquibasedb-secrets` | This sets the (admin) user that should be used to run Liquibase, if used in your service.
27
-
`liquibase.datasource.password` | set to the key `db.password` in secret `admin-liquibasedb-secrets` | This sets the (admin) user's password that should be used to run Liquibase, if used in your service.
28
-
`spring.datasource.username` | set to the key `db.username` in secret `customer32-db-secrets` | This sets the (regular) user for your application to use to connect to the database (if you use JPA or JDBC in your application).
29
-
`spring.datasource.password`: | set to the key `db.password` in secret `customer32-db-secrets` | This sets the (regular) user's password for your application to use to connect to the database (if you use JPA or JDBC in your application).
30
-
`DB_SERVICE` | set to the key `db.service` in secret `customer32-db-secrets` | This sets the database service name (the TNS name) for your application to use to connect to the database (if you use JPA or JDBC in your application).
31
-
`spring.datasource.url` | `jdbc:oracle:thin:@$(DB_SERVICE)?TNS_ADMIN=/oracle/tnsadmin` | This sets the data source URL for your application to use to connect to the database (if you use JPA or JDBC in your application).
32
-
`CONNECT_STRING` | `jdbc:oracle:thin:@$(DB_SERVICE)?TNS_ADMIN=/oracle/tnsadmin` | This sets the data source URL for your application to use to connect to the database (if you use JPA or JDBC in your application).
11
+
-`app.container.port`, for example `8080`.
12
+
This sets the listen port for the pod and service. The Spring Boot application will listen on this port. The default is `8080`. This can be set using the `--port` parameter on the `deploy` command in the CLI.
13
+
-`spring.profiles.active`, for example `default`.
14
+
This sets the Spring profiles that will be active in the application. The default value is `default`. This can be changed set the `--service-profile` parameter on the `deploy` command in the CLI.
15
+
-`spring.config.label`, for example `0.0.1`.
16
+
This is a label that can be used with Spring Config to look up externalized configuration from Spring Config Server, along with the application name and the profile.
17
+
-`eureka.instance.preferIpAddress`, for example `true`.
18
+
This tells the Eureka discovery client to use the `preferIpAddress` setting. This is required in Kubernetes so that service discover will work correctly.
19
+
-`eureka.instance.hostname`, for example `customer32.application`.
20
+
This sets the hostname that Eureka will use for this application.
21
+
-`MP_LRA_COORDINATOR_URL`, for example `http://otmm-tcs.otmm.svc.cluster.local:9000/api/v1/lra-coordinator`.
22
+
This is the URL for the transaction manager which is required when using Eclipse Microprofile Long Running Actions in your application.
23
+
-`MP_LRA_PARTICIPANT_URL`, for example `http://customer32.application.svc.cluster.local:8080`.
24
+
This is the participant URL which is required when using Eclipse Microprofile Long Running Actions in your application.
25
+
-`eureka.client.register-with-eureka`, for example `true`.
26
+
This tells the Eureka discovery client to register with the Eureka server.
27
+
-`eureka.client.fetch-registry`, for example `true`.
28
+
This tells the Eureka discovery client to make a local copy of the registry by fetching it from the Eureka server.
29
+
-`eureka.client.service-url.defaultZone`, for example `http://eureka.eureka:8761/eureka`.
30
+
This is the default zone for the Eureka discovery client.
31
+
-`zipkin.base-url`, for example `http://jaegertracing-collector.observability.svc.cluster.local:9411/api/v2/spans`.
32
+
This is the URL of the Zipkin-compatible trace collector which can be used by your application to send trace data to the platform.
33
+
-`otel.exporter.otlp.endpoint`, for example `http://open-telemetry-opentelemetry-collector.open-telemetry:4318/v1/traces`.
34
+
This is the URL of the OpenTelemetry (OTLP protocol) trace collector which can be used by your application to send trace data to the platform.
35
+
-`config.server.url`, for example `http://config-server.config-server.svc.cluster.local:8080`.
36
+
This is the URL of the Spring Config Server provided by the platform.
37
+
-`liquibase.datasource.username`, for example set to the key `db.username` in secret `admin-liquibasedb-secrets`.
38
+
This sets the (admin) user that should be used to run Liquibase, if used in your service.
39
+
-`liquibase.datasource.password`, for example set to the key `db.password` in secret `admin-liquibasedb-secrets`.
40
+
This sets the (admin) user's password that should be used to run Liquibase, if used in your service.
41
+
-`spring.datasource.username`, for example set to the key `db.username` in secret `customer32-db-secrets`.
42
+
This sets the (regular) user for your application to use to connect to the database (if you use JPA or JDBC in your application).
43
+
-`spring.datasource.password`:, for example set to the key `db.password` in secret `customer32-db-secrets`.
44
+
This sets the (regular) user's password for your application to use to connect to the database (if you use JPA or JDBC in your application).
45
+
-`DB_SERVICE`, for example set to the key `db.service` in secret `customer32-db-secrets`.
46
+
This sets the database service name (the TNS name) for your application to use to connect to the database (if you use JPA or JDBC in your application).
47
+
-`spring.datasource.url`, for example `jdbc:oracle:thin:@$(DB_SERVICE)?TNS_ADMIN=/oracle/tnsadmin`.
48
+
This sets the data source URL for your application to use to connect to the database (if you use JPA or JDBC in your application).
49
+
-`CONNECT_STRING`, for example `jdbc:oracle:thin:@$(DB_SERVICE)?TNS_ADMIN=/oracle/tnsadmin`.
50
+
This sets the data source URL for your application to use to connect to the database (if you use JPA or JDBC in your application).
0 commit comments