Make packages baked into images by Amigo visible to the service catalogue

.env

@@ -32,6 +32,9 @@ CQ_GITHUB_LANGUAGES=0.0.5
 # See https://github.com/guardian/cq-source-ns1
 CQ_NS1=0.1.2
 
+# See https://github.com/guardian/cq-image-packages
+CQ_IMAGE_PACKAGES=1.0.0
+
 # --- FOR LOCAL DEVELOPMENT ONLY ---
 STAGE=DEV
 DATABASE_USER=postgres

docs/cloudquery-implementation.md

@@ -10,6 +10,7 @@ We are using CloudQuery to collect data from:
 - Snyk
 - Fastly
 - Galaxies of the Guardian
+- Image packages
 
 As it is relatively easy collect data with CloudQuery, we have, largely, opted to collect _all_ the data.
 By collecting this extra data, we enable others to answer their questions. For example:
@@ -20,7 +21,7 @@ By collecting this extra data, we enable others to answer their questions. For e
 
 We have implemented CloudQuery to run on AWS ECS, 
 writing data to [Postgres](https://www.cloudquery.io/docs/plugins/destinations/postgresql/overview).
-This is all [defined using GuCDK](../packages/cdk/lib/cloudquery.ts).
+This is all [defined using GuCDK](../packages/cdk/lib/cloudquery/index.ts).
 
 We have more interest in some data sources than others.
 For example, we'd like to know more about AWS Lambdas across the estate than AWS Elastic Beanstalk deployments.

docs/getting-started.md

@@ -9,6 +9,7 @@ We are using CloudQuery to collect data about how The Guardian uses:
 - Snyk
 - Fastly
 - Galaxies of the Guardian
+- Image packages
 
 CloudQuery generally collects metadata about these resources. That means that we have information like the name of a
 repository, and when it was created, but not the contents of the files in it.