Documentation ¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type CMD ¶
type CMD struct { Name string Usage Usage Params []string // Just the parameters name Function func(...interface{}) }
Stores the given command
type DockerCompose ¶
type DockerCompose struct {
// contains filtered or unexported fields
}
type Dockerfile ¶
type Dockerfile struct {
// contains filtered or unexported fields
}
type Env ¶
type Env struct {
// contains filtered or unexported fields
}
func CreateEnv ¶
CreateEnv Goes trough the process of checking whether or not a environment variable is properly declared -- even tho doesn't check whether or not is "valid" in a way to check whether the source value exists or the destiny value is required or not. It returns a Environment Variable object and whether or not some error occurred
type Objectives ¶
type Objectives struct {
// contains filtered or unexported fields
}
type Project ¶
type Project struct {
// contains filtered or unexported fields
}
func LexProject ¶
LexProject just reads the given Succubus config file and checks it whether or not it's a valid one. It returns whether or not the config file is valid and any error encountered.
func Load ¶
Load checks for: 1. whether or not the project is has ambient issues 2. whether or not the project is has declaration issues 3. whether or not the project is has Project pattern issues It returns whether or not the Project is ok
func ParseProject ¶
ParseProject goes trough the "logic" behind a Succubus' configuration file. It's important tho to point out that this or any other function presented in this package checks whether or not the given command is "plausible" just if all the key have a string as a value; if a image tag points to a non-existing image or if a command is wrongfull typed or even not exists, this function doesn't perform this kind of pre-processing due to the runtime nature of those tasks. It returns the processed config file
func SemanticAnalysis ¶
SemanticAnalysis goes trough a Project definition and checks for:
- commands/variables ambiguity
- whether or not the current Project is from a different pattern from the one defined as the one to be followed
It returns the sanitized version of the Project or the error related to it
type WindowsContainers ¶
type WindowsContainers struct { }