Skip to content

Updated Dependency Management and add a new function to list all keys across all nodes in the Memcached cluster. #5

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

thompsonlabs
Copy link

1)Migrated the project away from Glide (which is no longer being actively maintained) to use the newer dependency management features provide by the Go Modules system.

2)Added new lister utility component and integrated it into the main ElastiCache class; its functionality is accessible via the new top-level ListAllKeys function.

Giles Thompson and others added 4 commits April 21, 2021 01:44
… now mostly unmaintained) to the newer Go Modules based dependency management which utilises go.mod and go.sum files respectfully. It is important to note that the team behind the Glide project themselves, recommend that developers migrate to Go Module for dependency management. See: https://github.com/Masterminds/glide
…o allow for the listing of ALL keys across ALL nodes in a cluster. The component has been fully integrated into the main elasticache class, its functionality acessible by the new ListAllKeys function.
…asticache Endpoint environment variable to be specified. The rationale behind this is to permit each instance of the Elasticache component to be associated with their own endpoint. Prior to this ALL instances of this Elasticache component would point to the SAME endpoint thereby prohibiting multiple caches to be referenced by a single application, this update now makes working with multiple memcache clusters possible.
…her than the list itself as a literal. Also initialised the arrays that is returned to an initial count of zero, it will be dynamically scaled according to the number of nodes that are returned from the listing operation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant