maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/pkg/compiler/errors/planapply.go

28 lines
1.7 KiB
Go
Raw Normal View History

Clarify aspects of using the DCO
2017-06-26 23:46:34 +02:00
// Copyright 2016-2017, Pulumi Corporation. All rights reserved.
Implement the `mu apply` command This change implements `mu apply`, by driving compilation, evaluation, planning, and then walking the plan and evaluating it. This is the bulk of marapongo/mu#21, except that there's a ton of testing/hardening to perform, in addition to things like progress reporting.
2017-02-19 20:41:05 +01:00
package errors
// Plan and apply errors are in the [2000,3000) range.
var (
Implement snapshot MuGL This change adds support for serializing snapshots in MuGL, per the design document in docs/design/mugl.md. At the moment, it is only exposed from the `mu plan` command, which allows you to specify an output location using `mu plan --output=file.json` (or `-o=file.json` for short). This serializes the snapshot with monikers, resources, and so on. Deserialization is not yet supported; that comes next.
2017-02-22 03:31:43 +01:00
ErrorCantCreateCompiler = newError(2000, "An error occurred during compiler construction: %v")
ErrorCantReadPackage = newError(2001, "An error occurred while reading the package '%v': %v")
Shorten an error message
2017-03-23 16:15:10 +01:00
ErrorCantCreateSnapshot = newError(2002, "A problem was found during planning: %v")
Implement snapshot MuGL This change adds support for serializing snapshots in MuGL, per the design document in docs/design/mugl.md. At the moment, it is only exposed from the `mu plan` command, which allows you to specify an output location using `mu plan --output=file.json` (or `-o=file.json` for short). This serializes the snapshot with monikers, resources, and so on. Deserialization is not yet supported; that comes next.
2017-02-22 03:31:43 +01:00
ErrorPlanApplyFailed = newError(2003, "Plan apply failed: %v")
ErrorIllegalMarkupExtension = newError(2004, "Resource serialization failed; illegal markup extension '%v'")
Reorganize deployment commands As part of pulumi/coconut#94 -- adding targeting capabilities -- I've decided to (yet again) reorganize the deployment commands a bit. This makes targets ("husks") more of a first class thing. Namely, you must first initialize a husk before using it: $ coco husk init staging Coconut husk 'staging' initialized; ready for deployments Eventually, this is when you will be given a choice to configure it. Afterwards, you can perform deployments. The first one is like a create, but subsequent ones just figure out the right thing to do and do it: $ ... make some changes ... $ coco husk deploy staging ... standard deployment progress spew ... Finally, should you want to teardown an entire environment: $ coco husk destroy staging ... standard deletion progress spew for all resources ... Coconut husk 'staging' has been destroyed!
2017-02-26 20:20:14 +01:00
ErrorCantReadDeployment = newError(2005, "Could not read deployment file '%v': %v")
Rename Monikers to URNs This change is mostly just a rename of Moniker to URN. It does also prefix resource URNs to have a standard URN namespace; in other words, "urn:coconut:<name>", where <name> is the same as the prior Moniker. This is a minor step that helps to prepare us for pulumi/coconut#109.
2017-03-03 02:10:10 +01:00
ErrorDuplicateURNNames = newError(2006, "Duplicate objects with the same URN: %v")
Use `Stack` over `Environment` to describe a deployment target Previously we used the word "Environment" as the term for a deployment target, but since then we've started to use the term Stack. Adopt this across the CLI. From a user's point of view, there are a few changes: 1. The `env` verb has been renamed to `stack` 2. The `-e` and `--env` options to commands which operate on an environment now take `-s` or `--stack` instead. 3. Becase of (2), the commands that used `-s` to display a summary now only support passing the full option name (`--summary`). On the local file system, we still store checkpoint data in the `env` sub-folder under `.pulumi` (so we can reuse existing checkpoint files that were written to the old folder)
2017-10-16 21:04:35 +02:00
ErrorInvalidStackName = newError(2007, "Stack '%v' could not be found in the current workspace")
Support config maps This change adds support for configuration maps. This is a new feature that permits initialization code to come from markup, after compilation, but before evaluation. There is nothing special with this code as it could have been authored by a user. But it offers a convenient way to specialize configuration settings per target husk, without needing to write code to specialize each of those husks (which is needlessly complex). For example, let's say we want to have two husks, one in AWS's us-west-1 region, and the other in us-east-2. From the same source package, we can just create two husks, let's say "prod-west" and "prod-east": prod-west.json: { "husk": "prod-west", "config": { "aws:config:region": "us-west-1" } } prod-east.json: { "husk": "prod-east", "config": { "aws:config:region": "us-east-2" } } Now when we evaluate these packages, they will automatically poke the right configuration variables in the AWS package *before* actually evaluating the CocoJS package contents. As a result, the static variable "region" in the "aws:config" package will have the desired value. This is obviously fairly general purpose, but will allow us to experiment with different schemes and patterns. Also, I need to whip up support for secrets, but that is a task for another day (perhaps tomorrow).
2017-02-28 04:43:54 +01:00
ErrorIllegalConfigToken = newError(2008,
Fix an assert and a message This change makes node optional in the lookupBasicType function, which is necessary in cases where diagnostics information isn't available (such as with configuration application). This eliminates an assert when you fat- finger a configuration key. The associated message was missing apostrophes.
2017-03-31 00:06:55 +02:00
"Configs may only target module properties and class static properties; '%v' is neither")
Add a pre-pass to validate resources before creating/updating This change adds a new Check RPC method on the provider interface, permitting resource providers to perform arbitrary verification on the values of properties. This is useful for validating things that might be difficult to express in the type system, and it runs before *any* modifications are run (so failures can be caight early before it's too late). My favorite motivating example is verifying that an AWS EC2 instance's AMI is available within the target region. This resolves pulumi/coconut#107, although we aren't using this in any resource providers just yet. I'll add a work item now for that...
2017-03-03 03:15:38 +01:00
ErrorConfigApplyFailure = newError(2009, "One or more errors occurred while applying '%v's configuration")
Catch duplicate URNs during planning We fail very late in the process of plan application, should a duplicate URN arise. This change fails as early in the process as possible and ensures that it does so with good line number information.
2017-06-27 22:04:06 +02:00
ErrorDuplicateResourceURN = newError(2010, "Duplicate resource URN '%v'; try giving it a unique name")
ErrorResourceInvalid = newError(2012, "%v resource '%v' has a problem: %v")
ErrorResourcePropertyInvalidValue = newError(2013, "%v resource '%v's property '%v' value %v has a problem: %v")
ErrorAnalyzeFailure = newError(2014, "Analyzer '%v' reported an error: %v")
ErrorAnalyzeResourceFailure = newError(2015,
Add the ability to specify analyzers This change adds the ability to specify analyzers in two ways: 1) By listing them in the project file, for example: analyzers: - acmecorp/security - acmecorp/gitflow 2) By explicitly listing them on the CLI, as a "one off": $ coco deploy <env> \ --analyzer=acmecorp/security \ --analyzer=acmecorp/gitflow This closes out pulumi/coconut#119.
2017-03-11 19:07:34 +01:00
"Analyzer '%v' reported a resource error:\n"+
"\tResource: %v\n"+
"\tProperty: %v\n"+
"\tReason: %v")
Implement the `mu apply` command This change implements `mu apply`, by driving compilation, evaluation, planning, and then walking the plan and evaluating it. This is the bulk of marapongo/mu#21, except that there's a ton of testing/hardening to perform, in addition to things like progress reporting.
2017-02-19 20:41:05 +01:00
)
Reference in a new issue Copy permalink