how to re-run CI/CD for EDSC (rebuild/redeploy)
- navigate to the deployment project environment for earthdata search: https://ci.earthdata.nasa.gov/deploy/viewDeploymentProjectEnvironments.action?id=242712580
- each release corresponds to a tag on https://github.com/nasa/earthdata-search/tags
- deployment usually takes roughly 15 minutes
how to change environmental variables (Bamboo variables)
- log into deployment project environment at https://ci.earthdata.nasa.gov/
- open up configuration
- click variables
- edit variables and save
- note: you will have to re-deploy in order to pick up environmental variable changes
how to pin or update dependency versions
- NPM uses semantic versioning
- More about how to specify versions of dependencies: https://docs.npmjs.com/cli/v9/configuring-npm/package-json#dependencies
- open package.json, update the versions in the "dependencies" or "devDependencies" object
- if you want to pin to a specific version, remove the "^" from beginning of the version string
- alternatively, you can run "npm audit fix"
- re-run npm install in order to get a new version of the package-lock.json file
- make sure to commit the package-lock.json file in addition to the package.json file
- note: you can use Snyk's built in "fix this vulnerability" button whereby Snyk will try to update the dependency versions and issue a PR. it often breaks builds, so it will require modification after the PR is submitted
how to log into Snyk and view vulnerability reports
- https://app.snyk.io/org/esdis-cumulus-core-gibs-cmr-etc.
- In order to navigate to vulnerability reports for specific Pull Requests:
- go to https://github.com/nasa/earthdata-search/pulls and open up the specific PR on Github
- scroll down to checks
- find security/snyk and click details
how to back-port vulnerability fixes:
how to backup and restore database for EDSC:
contact tree (aka phone tree):
- Alicia is the main POC
- Heather is backup to Alicia
Overview
Content Tools