Uses of Package
gov.nasa.pds.registry.common.connection.config

Packages that use gov.nasa.pds.registry.common.connection.config

Package	Description
gov.nasa.pds.registry.common.connection
gov.nasa.pds.registry.common.connection.config

Classes in gov.nasa.pds.registry.common.connection.config used by gov.nasa.pds.registry.common.connection

Class	Description
CognitoType	Currently, cognito to serverless opensearh requires three bits of information: 1. clientID: magic ID which must be given and is not a secret but sure looks like one 3. endpoint: the endpoint for serverless opensearch 2.
DirectType	Currently, connecting to an opensearch service directly requires just two pieces of information: 1.
Ec2Type	EC2 instances that have their IAM roles setup to match the cognito information when instantiated can use TCP/IP to share their credentials directly with their subprocess.

Classes in gov.nasa.pds.registry.common.connection.config used by gov.nasa.pds.registry.common.connection.config

Class	Description
CognitoType	Currently, cognito to serverless opensearh requires three bits of information: 1. clientID: magic ID which must be given and is not a secret but sure looks like one 3. endpoint: the endpoint for serverless opensearch 2.
DirectType	Currently, connecting to an opensearch service directly requires just two pieces of information: 1.
Ec2Type	EC2 instances that have their IAM roles setup to match the cognito information when instantiated can use TCP/IP to share their credentials directly with their subprocess.
RegistryConnection	This terrible construct is so that xjc can autodetect this as the root node for processing.