Expected behavior
The expected behaviour should be that it shows any campaign that's currently a 'create' draft that is also 'in admin review' from the production MI.
Downstream weirdness of not having deployed the backend:
We deployed the production frontend with a link to the staging API, which causes the request to /api/upcoming_drafts to fail since it violates the Content Security Policy. This is correct, since we don't want to display data from staging, anyway.
We deployed to production with a link to staging because we don't have github environments set up on this repo, so we only have one set of Secrets. We configure the URL for the ADMG API in github actions using secrets.GATSBY_ADMG_API. Because we don't have separate environments set up, that values is the same for both staging and production deployments.
### Tasks
- [ ] Deploy admg-backend to production, to enable the unpublished drafts endpoint
- [ ] Set up Github Environments on this repo, so we can define separate sets of secrets for staging and production
- [ ] Redeploy the frontend with the correct URL for the ADMG API
Describe the bug The coming soon page we implemented https://github.com/NASA-IMPACT/admg-casei/issues/507 is expected to show users campaigns that are in admin review. But we aren't seeing anything listed.
To Reproduce Steps to reproduce the behavior:
Expected behavior The expected behaviour should be that it shows any campaign that's currently a 'create' draft that is also 'in admin review' from the production MI.
It should show this campaign in production: https://admg.nasa-impact.net/drafts/campaign?action=Create&status=4&short_name=
Screenshots No visible coming soon items
Expected 1 campaign item with 'draft' status 'awaiting admin review'
Additional context Paper trail of findings
dev
toproduction
onadmg-backend
in order to enable this feature: https://github.com/NASA-IMPACT/admg-backend/pull/547Downstream weirdness of not having deployed the backend:
/api/upcoming_drafts
to fail since it violates the Content Security Policy. This is correct, since we don't want to display data from staging, anyway.secrets.GATSBY_ADMG_API
. Because we don't have separate environments set up, that values is the same for both staging and production deployments.Acceptance Criteria