Goal: 

• Have content-sources communicating with candelpin

Acceptance Criteria:

• Figure out how to add candlepin to our docker-compose (https://quay.io/repository/candlepin/candlepin?tab=tags) ?
• Create a new repo for the client, maybe use a term from https://www.everythingcandlepin.com/glossary/ 
  • Candlepin doesn't get updated very often, so we can probably just manually check in a new openapi.yaml file and version number on update

  • docker run --network=host --rm -v ${PWD}:/local openapitools/openapi-generator-cli:latest-release generate           -i /local/candlepin-api-spec.yaml  -g go   --git-user-id=content-services --git-repo-id=candlepin --package-name=candlepin   -o /local/release
    
    
    
    

     

• Add connection under clients in config
• Integrate this in with content-sources via a helper application:

• • ./cmd/candlepin/main.go create  $ORG_ID
• This should create an organization.  In stage/prod the orgs will already be created.
• Investigate how this will work in ephemeral 

The '#teamnado'  slack channel should be very helpful

'Pino Toscano' may be helpful from the client side tooling team