Apply to Supply

Apply to Supply is a clone of the Digital Marketplace for supplier onboarding for G-Cloud 13 and Digital Outcomes 6. It’s also known as ‘Digital Marketplace 1.5’ and ‘DMP-SO’.

Suppliers can apply to G-Cloud 13 and Digital Outcomes 6 on Apply to Supply. All activity for other frameworks continues to be on the Digital Marketplace.

Any non-buyer logins that worked in the Digital Marketplace before Digital Outcomes 6 opened will work in Apply to Supply.

CCS people can access non-public documentation including the design, runbook, migration, and more.

Support

You need to repeat some processes in both the Digital Marketplace and Apply to Supply. For example, removing user data or adding new admins. Otherwise, support processes remain mostly the same.

Development

The code all lives in private repositories in our GitHub organisation. They all have a common naming pattern, starting with ‘ccs-’. Ask another member of the team for access to the relevant GitHub team.

Deployment

Apply to Supply has its own Jenkins, configured using Ansible.

Follow the same deployment process as for the Digital Marketplace. Just notify the #dmp-1-5-production Slack channel instead. Also, the pipeline doesn’t automatically deploy your changes to production once the staging tests have passed so you have an opportunity to test high-risk changes before they hit production.

Environments

Production is https://www.applytosupply.digitalmarketplace.service.gov.uk. Disaster recovery is https://www.applytosupply.crowncommercial.gov.uk. All other environments are https://www.<environment name>.marketplace.team.

AWS

Ask Internal IT for your login to the management account. You will be able to use that to switch roles to all our other AWS accounts.

TechOps have set up Terraform to manage the AWS accounts. Consult with them before making manual changes to any of the things covered by the Terraform.

Monitoring

Apply to Supply has a Grafana to monitor all environments. See prometheus/grafana-prod.yaml in the credentials repository for the credentials to access.

The Grafana pulls metrics from Prometheus. Neither use permanent storage. This means that we will lose historic metrics if the Prometheus instance is restarted or replaced. Similarly, we will lose the configured Grafana dashboards if the Grafana instance is restarted or replaced.

We have saved Grafana dashboards in the grafana directory in the digitalmarketplace-aws repository. To add one to Grafana, create a new dashboard and then go to Settings -> JSON Model. Copy in the dashboard from the repository, changing the id and uid to null and the version to 0. If you make changes to the dashboards, apply your changes to the saved copies in the repository to ensure they don’t get lost.

Logging

We ship our logs to logit.io. Ask Internal IT for access.