Create a new private library repository with the name helix-config
(note, I'd like to keep this repository private until "GA" but make it public once the config schema and API is stable )
this will provide
the common, runtime agnostic, config-service aggregation code that will be used by the node functions and cf workers
the json schemas and types for all the configuration
an node api to CRUD the configuration (which will eventually be used by the admin-service)
Stuff you can do yourself
[x] run npm init @adobe/helix-library or npm init @adobe/helix-service
[x] Add topics to the repository, at least helix
[x] Add the group "Project Helix Admins" with Admin permissions to the list of collaborators
[x] Add the group "Project Helix Developers" with Write permissions to the list of collaborators (Project Helix Guests will be taken care of automatically)
[ ] Uncomment and adjust the helix-post-deploy/monitoring command in .circleci/config.yaml: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://status.project-helix.io for reference.
[ ] Add a CIRCLECI_TOKEN to the repository secrets.
Create a new private library repository with the name
helix-config
(note, I'd like to keep this repository private until "GA" but make it public once the config schema and API is stable )
this will provide
Stuff you can do yourself
npm init @adobe/helix-library
ornpm init @adobe/helix-service
helix
for services
helix-post-deploy/monitoring
command in.circleci/config.yaml
: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://status.project-helix.io for reference.CIRCLECI_TOKEN
to the repository secrets.Stuff you need an Adobe Org Admin for
for libraries
ADOBE_BOT_NPM_TOKEN
org secret