Package com.kingsrook.qqq.backend.core.instances


package com.kingsrook.qqq.backend.core.instances
  • Class
    Description
    Version of AbstractQQQApplication that assumes all meta-data is produced by MetaDataProducers in (or under) a single package.
    Base class to provide the definition of a QQQ-based application.
    Version of AbstractQQQApplication that assumes all meta-data is defined in config files (yaml, json, etc) under a given directory path.
    Class-level annotation to declare what fields should run through the variable interpreter - e.g., to be replaced with env-var values at run-time.
    Version of AbstractQQQApplication that assumes all meta-data is produced by MetaDataProducers in (or under) a single package (where you can pass that package into the constructor, vs. the abstract base class, where you extend it and override the getMetaDataPackageName method.
    As part of helping a QInstance be created and/or validated, apply some default transformations to it, such as populating missing labels based on names.
    Utility methods for working with (dynamic, from a table) HelpContent - and putting it into meta-data in a QInstance.
    Object used to mark a QInstance has having been validated.
    Object used to record state of a QInstance having been validated.
    Class that knows how to take a look at the data in a QInstance, and report if it is all valid - e.g., non-null things are set; references line-up (e.g., a table's backend must be a defined backend).
    To avoid having secrets (passwords, access keys, etc) committed into meta data files, as well as to just let some meta data not be hard-coded, this class is used by the Enricher to "promote" values, such as ${env.ACCESS_KEY} to be read from the environment (or other secret providers (to be implemented)).
    Utility class for working with AWS Secrets Manager.