Skip to content

Commit

Permalink
Merge pull request #33 from cooperwalbrun/housekeeping
Browse files Browse the repository at this point in the history
Make Some Minor Clarifying Changes to the README
  • Loading branch information
cooperwalbrun authored May 10, 2024
2 parents 1713706 + c0a9b34 commit b232908
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Total 40960

With the `--prefix` argument, we can now query our available network space to our desired level of
detail. Note that if we specify a `--prefix` with a value lower than any of the prefixes in the
originally-returned list, those CIDRs will be skipped. For example, if we run the following:
available CIDRs list, those CIDRs will be skipped. For example, if we run the following:

```bash
aws-cidr-finder --profile myprofile --prefix 18
Expand All @@ -111,7 +111,7 @@ CIDR into one or more `/18` CIDRs.
## Installation

If you have Python >=3.10 and <4.0 installed, `aws-cidr-finder` can be installed from PyPI using
something like
something like this:

```bash
pip install aws-cidr-finder
Expand Down Expand Up @@ -189,7 +189,7 @@ for message in output["messages"]:
for cidr in output["cidrs_not_converted_to_prefix"]:
# If aws-cidr-finder could not convert a given available CIDR block into one or more CIDR blocks
# with the requested desired_prefix, it will be returned in this list
# Note: this is only applicable if you passed desired_prefix to find_available_cidrs
# Note: this list is only populated if you passed desired_prefix to find_available_cidrs
print(f"aws-cidr-finder did not convert the following CIDR block to the desired prefix: {cidr}")

for vpc in output["data"]:
Expand Down

0 comments on commit b232908

Please sign in to comment.