type
  • DescriptionThe type of repository used in this environment.

  • Type: Enumeration

    EnumerationDescription
    ARTIFACTORY

    Provide the Hostname, Port, Username/Password or the SSL Credentials of your Artifact repository.

    See your repository documentation to set up your Artifact repository.

    FTP

    Use your own FTP repository for application artifacts. See Artifact Repository for additional details.

    Provide the Hostname, Port, Username/Password of your FTP repository.

    The CloudCenter platform only supports PASSIVE mode when using FTP repositories.

    HTTP

    Use your own HTTP repository for application artifacts. See Artifact Repository for additional details.

    Provide the Hostname, Port, and optionally, Username/Password of your HTTP repository.

    You can create HTTP repositories using Apache, Nginx or any other web server of your choice. You can then use HTTP repositories to host application artifacts.

    HTTPS

    Use your own HTTPS repository for application artifacts. See Artifact Repository for additional details.

    Provide the Hostname and Port. You can choose to provide the username/password or SSL credentials that comprise of the Private Key, Client/Trusted certificates of your HTTPS repository.

    AMAZON_S_3Provide the Region, Access Key, Access Secret for your AWS account, and the name of the S3 Bucket, that you would like to use as your repository.
    PUPPET

    The central server that manages Puppet Agent(s). Refer to http://docs.puppetlabs.com (install Puppet) for additional context. This option is only displayed if you use the Puppet service. Provide the Hostname (of the Puppet primary server) and the Certname Suffix (authentication credentials for the Puppet primary server).

    CHEF

    The central server that manages the Chef clients. Refer to https://docs.chef.io/ (install server) for additional context. Alternately, you can also use the free Chef server image provided in the AWS Marketplace. This option is only displayed if you use the Chef service.

    Provide the Hostname, Chef User Key, Chef Validation key and optionally Trusted Certificate of the Chef Server.

    If your Chef Server is configured with a Public DNS, add the Public DNS in the Hostname field and copy the public DNS to the Trusted Certificate field when creating or editing the repository.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks