Quay Integration

The CoreOs Quay Integration is used to connect Shippable DevOps Assembly Lines platform to Quay Docker Registry so that you can pull and push Docker images.

Creating an Integration

You can add this integration by following steps on the Adding an integration page.

Here is the information you need to create this integration:

  • Integration type -- Quay.io
  • Name -- choose a friendly name for the integration
  • Username -- login to your Quay Account
  • Password -- password of your Quay Account
  • Email -- email of your Quay Account
  • Access Token -- access token of your Quay Account

Instructions to create access tokens are here.

Usage in CI

Usage in Assembly Lines

The Quay integration can be used in the following resources:

Default Environment Variables

When you create a resource with this integration, and use it as an IN or OUT for a runSh or runCI job, a set of environment variables is automatically made available that you can use in your scripts.

<NAME> is the the friendly name of the resource with all letters capitalized and all characters that are not letters, numbers or underscores removed. Any numbers at the beginning of the name are also removed to create a valid variable. For example, my-key-1 will be converted to MYKEY1, and my_key_1 will be converted to MY_KEY_1.

Environment variable Description
<NAME>_INTEGRATION_USERNAME Username supplied in the integration
<NAME>_INTEGRATION_PASSWORD Password supplied in the integration
<NAME>_INTEGRATION_EMAIL Email supplied in the integration
<NAME>_INTEGRATION_ACCESSTOKEN Access Token supplied in the integration

Shippable Utility Functions

The platform also provides a command line utility called shipctl that can be used to retrieve the values of these environment variables.

The specific function that can be used in the jobs yml is: shipctl get_integration_resource_field <resource name> <field name>.

Here is a table that provides the mapping from the environment variable to the field name.

Environment variable Field Name
<NAME>_INTEGRATION_USERNAME username
<NAME>_INTEGRATION_PASSWORD password
<NAME>_INTEGRATION_EMAIL email
<NAME>_INTEGRATION_ACCESSTOKEN accessToken

More information on other utility functions is documented here.

Further Reading