Update Readme with an example of filtering
@@ -31,6 +31,18 @@ $ cargo +nightly run -- generate -c ./services.json -o ../rusoto/services
This will regenerate all services in the `rusoto/services` directory, updating them with the configuration defined in the `services.json` file and applying any code generation changes.
+It is also possible to limit the set of services generated by the generator. For example, to only generate the s3 and ec2 crates,
+run the following:
+
+```bash
+$ cargo run -- generate -c ./services.json -o ../rusoto/services -s s3 -s ec2
+ Finished dev [optimized] target(s) in 0.35s
+ Running `target/debug/rusoto_service_crategen generate -c ./services.json -o ../rusoto/services -s s3 -s ec2`
+Generating crate for Amazon Simple Storage Service @ 2006-03-01...
+Generating crate for Amazon Elastic Compute Cloud @ 2016-11-15...
+```
+
+
## Customizing Generated Crates
Some service crates may require customized code, perhaps as helper code to make it easier to use for end-users or custom tests. Since services are regenerated by the generator, there needs to be a safe place for custom code to sit that won't be destroyed on regeneration.
