2016-11-15 20:30:34 +01:00
|
|
|
package: github.com/marapongo/mu
|
|
|
|
|
import:
|
|
|
|
|
- package: github.com/ghodss/yaml
|
|
|
|
|
- package: github.com/spf13/cobra
|
|
|
|
|
- package: github.com/spf13/pflag
|
|
|
|
|
- package: gopkg.in/yaml.v2
|
|
|
|
|
- package: github.com/golang/glog
|
|
|
|
|
- package: github.com/golang/lint
|
|
|
|
|
subpackages:
|
|
|
|
|
- golint
|
2016-11-16 04:18:03 +01:00
|
|
|
- package: github.com/stretchr/testify
|
2016-11-16 19:00:52 +01:00
|
|
|
- package: github.com/blang/semver
|
Sketch out more AWS backend code-generator bits and pieces
This change includes a few steps towards AWS backend code-generation:
* Add a BoundDependencies property to ast.Stack to remember the *ast.Stack
objects bound during Stack binding.
* Make a few CloudFormation properties optional (cfOutput Export/Condition).
* Rename clouds.ArchMap, clouds.ArchNames, schedulers.ArchMap, and
schedulers.ArchNames to clouds.Values, clouds.Names, schedulers.Values,
and schedulers.Names, respectively. This reads much nicer to my eyes.
* Create a new anonymous ast.Target for deployments if no specific target
was specified; this is to support quick-and-easy "one off" deployments,
as will be common when doing local development.
* Sketch out more of the AWS Cloud implementation. We actually map the
Mu Services into CloudFormation Resources; well, kinda sorta, since we
don't actually have Service-specific logic in here yet, however all of
the structure and scaffolding is now here.
2016-11-19 01:46:36 +01:00
|
|
|
- package: github.com/satori/go.uuid
|
Implement dependency resolution
This change includes logic to resolve dependencies declared by stacks. The design
is described in https://github.com/marapongo/mu/blob/master/docs/deps.md.
In summary, each stack may declare dependencies, which are name/semver pairs. A
new structure has been introduced, ast.Ref, to distinguish between ast.Names and
dependency names. An ast.Ref includes a protocol, base part, and a name part (the
latter being an ast.Name); for example, in "https://hub.mu.com/mu/container/",
"https://" is the protocol, "hub.mu.com/" is the base, and "mu/container" is the
name. This is used to resolve URL-like names to package manager-like artifacts.
The dependency resolution phase happens after parsing, but before semantic analysis.
This is because dependencies are "source-like" in that we must load and parse all
dependency metadata files. We stick the full transitive closure of dependencies
into a map attached to the compiler to avoid loading dependencies multiple times.
Note that, although dependencies prohibit cycles, this forms a DAG, meaning multiple
inbound edges to a single stack may come from multiple places.
From there, we rely on ordinary visitation to deal with dependencies further.
This includes inserting symbol entries into the symbol table, mapping names to the
loaded stacks, during the first phase of binding so that they may be found
subsequently when typechecking during the second phase and beyond.
2016-11-21 20:19:25 +01:00
|
|
|
- package: github.com/mitchellh/go-homedir
|
2016-11-25 21:58:29 +01:00
|
|
|
- package: github.com/Masterminds/sprig
|
|
|
|
|
- package: github.com/aokoli/goutils
|