c1b5239667
This change detects the target cloud earlier on in the compilation process. Prior to this change, we didn't know this information until the backend code-generation. Clearly we need to know this at least by then, however, templates can specialize on this information, so we actually need it sooner. This change moves it into the frontend part. Note that to support this we now eliminate the ability to specify target clusters in the Mufile alone. That "feels" right to me anyway, since Mufiles are supposed to be agnostic to their deployment environment, other than template specialization. Instead, this information can come from the CLI and/or the workspace settings file. |
||
---|---|---|
.. | ||
backend.go | ||
phase.go | ||
visitor.go |