...

Source file src/github.com/redhat-developer/odo/pkg/api/analyze.go

Documentation: github.com/redhat-developer/odo/pkg/api

     1  package api
     2  
     3  // DetectionResult indicates the result of an analysis against a given project.
     4  // Analysis might be performed via the Alizer backend or non-interactively via the Flags backend.
     5  // It contains detection analysis information such as the location of a devfile,
     6  // either in a devfile registry or using a path or a URI or the application ports if any.
     7  type DetectionResult struct {
     8  	// name of the Devfile in Devfile registry (required if DevfilePath is not defined)
     9  	Devfile string `json:"devfile,omitempty"`
    10  
    11  	// name of the devfile registry (as configured in odo registry). It can be used in combination with Devfile, but not with DevfilePath (optional)
    12  	DevfileRegistry string `json:"devfileRegistry,omitempty"`
    13  
    14  	// path to a devfile. This is alternative to using devfile from Devfile registry. It can be local filesystem path or http(s) URL (required if Devfile is not defined)
    15  	DevfilePath string `json:"devfilePath,omitempty"`
    16  
    17  	// ApplicationPorts represents the list of ports detected
    18  	ApplicationPorts []int  `json:"ports,omitempty"`
    19  	DevfileVersion   string `json:"devfileVersion,omitempty"`
    20  	// Name represents the project/application name as detected by alizer
    21  	Name string `json:"name,omitempty"`
    22  	// Architectures represent the architectures with which the Devfile must be compatible with.
    23  	Architectures []string `json:"architectures,omitempty"`
    24  }
    25  

View as plain text