Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: change "already bootstrapped" message #1180

Merged
merged 3 commits into from
Nov 15, 2018

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Nov 15, 2018

The previous wording, with the word "fully" in it and the exclamation mark at the end, sounded vaguely accusatory.

To my (admittedly non-native speaking) senses, the exchange feels akin to this:

$ cdk do-something
Didn't you know? It's already COMPLETELY done, silly!

Instead of just always saying "successfully bootstrapped", I do want to keep a sense of "nothing has been done" in there, to avoid giving some potential subset of people the false impression that they need to do bootstrap+deploy every time.

This is my stab at an alternative wording.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

The previous wording, with the word "fully" in it and the exclamation mark at the end, sounded vaguely accusatory.

To my (admittedly non-native speaking) senses, the exchange feels akin to this:

```
$ cdk do-something
Didn't you know? It's already COMPLETELY done, silly!
```

Instead of just always saying "successfully bootstrapped", I do want to keep a sense of "nothing has been done" in there, to avoid giving some potential subset of people the false impression that they need to do `bootstrap+deploy` every time.

This is my stab at an alternative wording.
@@ -281,8 +281,8 @@ async function initCommandLine() {
success(' ⏳ Bootstrapping environment %s...', colors.blue(environment.name));
try {
const result = await bootstrapEnvironment(environment, aws, toolkitStackName, roleArn);
const message = result.noOp ? ' ✅ Environment %s was already fully bootstrapped!'
: ' ✅ Successfully bootstrapped environment %s!';
const message = result.noOp ? ' ✅ Environment %s already bootstrapped, nothing to do.'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would tend to shift the "nothing to do" upfront (it's the main info, I guess at this point).

Nothing to do: environment %s was already bootstrapped.

You might want to also apply the same polish to the deployment messaging (they are based off a very similar template).

@rix0rrr rix0rrr merged commit 020743b into master Nov 15, 2018
@rix0rrr rix0rrr deleted the huijbers/bootstrapped-wording branch November 15, 2018 14:10
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants