Skip to content

Conversation

@gadomski
Copy link

@gadomski gadomski commented Nov 24, 2025

Description

I've opened this branch against microsoft#346 to re-use the directory and collection templates. This is my best-guess of how this will work until I can test it against a system.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

TODO

Checklist:

Please delete options that are not relevant.

  • I have performed a self-review
  • Changelog has been updated
  • Documentation has been updated
  • Unit tests pass locally (./scripts/test): Can't run the tests, and docker compose up fails 😢
  • Code is linted and styled (./scripts/format): Fails with network pctasks-network declared as external, but could not be found, and docker compose up fails 😢

@gadomski gadomski marked this pull request as ready for review December 4, 2025 16:33
@gadomski gadomski changed the title feat(wip): updates to process items, etc feat: create items for uk met office Dec 4, 2025
@ghidalgo3
Copy link

ghidalgo3 commented Dec 4, 2025

I'm going to set up a secret called STAGING_DB_CONNECTION_STRING in the pctasks key vault. When you submit the workflows to the production pctasks server to create the collection and ingest items, you will need to set an environment variable in the workflow DB_CONNECTION_STRING to the value of secrets.STAGING_DB_CONNECTION_STRING. I'll create that secret and let you know when it's ready to use.

If you don't override the secret, collections and items will be written to the prod database, which we don't want yet.

@ghidalgo3
Copy link

The secret has been created, it's called staging-db-connection-string , please try using that connection string and let us know if it works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants