Uses of Package
com.yahoo.config.application.api
Package
Description
-
ClassDescriptionAn application file represents a file within an application package.Metadata about an application package.Represents an application package, that is, used as input when creating a VespaModel and as a general reference to all contents in an application.Defines the BCP structure for an instance in a deployment spec: A list of region groups where each group contains a set of regions which will handle the traffic of a member in the group when it becomes unreachable.Describes a component residing in the components directory.Used during application deployment to propagate messages to the end userThe deployment spec for an application instanceSpecifies the environments and regions to which an application should be deployed.A blocking of changes in a given time windowA deployment step which is to run deployment in a particular zoneRepresents a deprecated XML element in
DeploymentSpec
, or the deprecated attribute(s) of an element.Determines when application changes deploy.Determines what application changes to deploy to the instance.A deployment stepA container for several steps, by default in serial orderControls when this application will be upgraded to new Vespa versionsDetermines when application changes deploy, when there is already an ongoing platform upgrade.Represents an application- or instance-level endpoint in deployments.xml.The level of targets in an endpointA target of an endpointConfiguration of notifications for deployment jobs.This class represents a window of time for selected hours, days and dates.A range of local dates, which may be unboundedA config definition that has not been parsed.Ids of validations that can be overriddenA set of allows which suppresses specific validations in limited time periods.A validation override which allows a particular change. -
ClassDescriptionSpecifies the environments and regions to which an application should be deployed.
-
ClassDescriptionRepresents an application package, that is, used as input when creating a VespaModel and as a general reference to all contents in an application.Used during application deployment to propagate messages to the end userIds of validations that can be overridden