YAML de ejemplo - Plugin Omma Data (Aqtiva)

####################################################################################################
# Example YAML for Tot Plugin OmmaData / Omma Data                                                 #
#                                                                                                  #
# This file has all the technical properties that can be edited for the client.                    #
# These properties have a default value in the application,                                        #
# so there is no necessity to configure them.                                                      #
# Only configure these properties if they are going to be different to the value of this file,     #
# this will make your files more clean and readable.                                               #
####################################################################################################
#########################
###  Logs properties  ###
#########################
logging:
  pattern:
    # Pattern to convert logs in the convenient format for the client
    console: "%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){faint} [TOT-PLUGIN-OMMADATA] %clr(${LOG_LEVEL_PATTERN:%5p}) %clr(${PID:- }){magenta} %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %m%n${LOG_EXCEPTION_CONVERSION_WORD:%wEx}"
  # Mark the level of log to show for every package. ERROR > WARN > INFO > DEBUG > TRACE
  level:
    # The main log level this is the base for all logs
    root: info
    # Every package of code can be marked with a different log level, every package of code printed on log is selectable to have a record here and mark a log level
    com.anjana: DEBUG

#########################
### Server properties ###
#########################
server:
  # the port where the service will be listening to
  port: 15020

#############################
### Tot Plugin properties ###
#############################
totplugin:
  server:
    # the tot server list of URLs, tot can have more than one instance running.
    urls:
      - https://tot1server.anjanadata.local/totserver/
  # list of aris to define the different plugin functionalities
  aris:
    - ari: "anja:totplugin:extract:/jdbc/ommadata/devQA"
###########################################
### Own properties of the OmmaData plugin ###
###########################################

  ommadata:
    # If we want to avoid the validation of certificates in requests to OmmaData (always true in production or remove this property)
    enable-certs-validation: false
    # OmmaData API url
    url: http(s)://<ommadata_domain>:<ommadata_port>/<context>
    auth:
      # OmmaData authentication properties
      url: http(s)://<ommadata_domain>:<ommadata_port>/public/auth/login
      client-id: <client_id>
      secret: <client_secret>
    # Synchronisation execution schedule with OmmaData. Cron format: <seconds> <minutes> <hours> <day-of-month> <month> <day-of-week>
    scheduling: 0 */1 7-22 * * MON-FRI
    # Delta to be added to the last execution date. The result date will be used to request the data in OmmaData
    synchronization:
      delta: 5
      unit: SECONDS # ChronoUnit format: MILLIS, SECONDS, MINUTES, HOURS, DAYS

#################################
### Hecate(Eureka) properties ###
#################################
eureka:
  client:
    serviceUrl:
      # the url where Hecate is listening. Plugins use Anjana's Hecate server so they need to use Tot as proxy
      defaultZone: https://tot1server.anjanadata.local/totserver/