-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
24 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,16 @@ | ||
/* | ||
Package raws | ||
Package raws currently provides simplicity - one package vs multitude in AWS - | ||
as well as multi-region management - all calls are done for each selected region(s). | ||
Region's parameter also supports globbing, thus allowing to fetch data from all | ||
eu with: 'eu-*' or all eu-west with 'eu-west-*' | ||
Raws currently provides simplicity - one package vs multitude in AWS - as well as multi-region management - all calls are done for each selected region(s). Region's parameter also supports globbing, thus allowing to fetch data from all eu with: 'eu-*' or all eu-west with 'eu-west-*' | ||
Currently only a couple of the most used information is gathered, but adding extra | ||
calls should not be complicated, as they all have the same logic. | ||
Currently only a couple of the most used information is gathered, but adding extra calls should not be complicated, as they all have the same logic. | ||
For the sake of avoiding repetitive documentation, each function that this package contains with the context.Context type as a first parameter, won't be documented, at least if there is not special usage of it inside of the function, because the context.Context is provided for implementing the most adopted concurrency pattern, used by the Go community (see https://blog.golang.org/context). | ||
For the sake of avoiding repetitive documentation, each function that this package | ||
contains with the context.Context type as a first parameter, won't be documented, | ||
at least if there is not special usage of it inside of the function, because the | ||
context.Context is provided for implementing the most adopted concurrency pattern, | ||
used by the Go community (see https://blog.golang.org/context). | ||
*/ | ||
package raws |