b57e4c4414
This change introduces the notion of "Stack subclassing" in two ways:
1. A Stack may declare that it subclasses another one using the base property:
name: mystack
base: other/stack
.. as before ..
2. A Stack may declare that it is abstract; in other words, that it is meant
solely for subclassing, and cannot be compiled and deployed independently:
name: mystack
abstract: true
.. as before ..
Note that non-abstract Stacks are required to declare at least one Service,
whether that is public, private, or both.
22 lines
474 B
Go
22 lines
474 B
Go
// Copyright 2016 Marapongo, Inc. All rights reserved.
|
|
|
|
package errors
|
|
|
|
import (
|
|
"github.com/marapongo/mu/pkg/diag"
|
|
)
|
|
|
|
var SymbolAlreadyExists = &diag.Diag{
|
|
ID: 500,
|
|
Message: "A symbol already exists with the name '%v'",
|
|
}
|
|
|
|
var TypeNotFound = &diag.Diag{
|
|
ID: 501,
|
|
Message: "Type '%v' was not found",
|
|
}
|
|
|
|
var NonAbstractStacksMustDefineServices = &diag.Diag{
|
|
ID: 502,
|
|
Message: "Non-abstract stacks must declare at least one private or public service",
|
|
}
|