-
Notifications
You must be signed in to change notification settings - Fork 303
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
README Changes for v1.0.0 #370
Conversation
… configure information.
6214c93
to
2868e96
Compare
0989492
to
fb6dff0
Compare
fb6dff0
to
df51e1d
Compare
README.md
Outdated
|
||
### Cluster Configurations | ||
|
||
A cluster configuration is a set of fields that describes an Amazon ECS cluster including the name of the cluster and the region. These configurations can then be referenced when you run Amazon ECS CLI commands using the `--cluster-config` flag otherwise the default configuration is used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- A cluster configuration is the* set of fields
- comma before "including"
- Semicolon after
--cluster-config
flag and before "otherwise"
README.md
Outdated
|
||
USAGE: | ||
command configure [command options] [arguments...] | ||
The Amazon ECS CLI supports the configuring of multiple sets of AWS credentials as named profiles using the `ecs-cli configure profile command`. These profiles can then be referenced when you run Amazon ECS CLI commands that require credentials using the `--ecs-profile` flag otherwise the default profile is used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Suggested rephrase: The Amazon ECS CLI supports configuring multiple sets
- Give example of cli commands that require credentials?
- semicolon before "otherwise", or rephrase to say "If a custom profile is not specified, the default profile will be used."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few copy-edits (careful of your run-on sentences!) Also, for purposes of review, it's easier to break up long sentences with line breaks in the README.
Shall we also run this by @nrdlngr?
README.md
Outdated
--compose-service-name-prefix "ecscompose-service-" [Optional] Specifies the prefix added to an ECS service created from a compose file. Format <prefix><project-name>. | ||
--cfn-stack-name-prefix "amazon-ecs-cli-setup-" [Optional] Specifies the prefix added to the AWS CloudFormation stack created on ecs-cli up. Format <prefix><cluster-name>. | ||
``` | ||
Set up a CLI profile with the following command, substituting `profile_name` with your desired profile name, `$AWS_ACCESS_KEY_ID` and `$AWS_SECRET_ACCESS_KEY` environment variables with your AWS credentials. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awkwardly phrased. Needs an "and" after "profile name" perhaps?
README.md
Outdated
|
||
A cluster configuration is a set of fields that describes an Amazon ECS cluster including the name of the cluster and the region. These configurations can then be referenced when you run Amazon ECS CLI commands using the `--cluster-config` flag otherwise the default configuration is used. | ||
|
||
Create a cluster configuration with the following command, substituting `region_name` with your desired AWS region, `cluster_name` with the name of an existing Amazon ECS cluster or a new cluster to use, and `configuration_name` for the name you'd like to give this configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're going to use "substitute with" in the first, two, maybe be consistent for the last one (instead of using "substitute for")
README.md
Outdated
|
||
### Using Credentials from `~/.aws/credentials`, Assuming a Role, and Multi-Factor Authentication | ||
|
||
The `--aws-profile` flag and `$AWS_PROFILE` environment variable allows you to reference any named profile in `~/.aws/credentials`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"allow" (since the subject of the sentence is both flag and variable)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
README.md
Outdated
|
||
USAGE: | ||
command configure [command options] [arguments...] | ||
The Amazon ECS CLI supports configuring multiple sets of AWS credentials as named profiles using the `ecs-cli configure profile command`. These profiles can then be referenced when you run Amazon ECS CLI commands using the `--ecs-profile` flag; If a custom profile is not specified, the default profile will be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Either use a period instead of semicolon before "If", or lowercase the "If".
Partially addresses questions in #372, #369, #284