Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

catalog links return 404 #139

Open
pindge opened this issue Dec 2, 2021 · 1 comment
Open

catalog links return 404 #139

pindge opened this issue Dec 2, 2021 · 1 comment
Assignees

Comments

@pindge
Copy link
Contributor

pindge commented Dec 2, 2021

Expected behaviour

ci working

Actual behaviour

the two links all return 404 https://raw.githubusercontent.com/GeoscienceAustralia/dea-config/master/workspaces/sandbox-metadata.yaml

https://github.com/GeoscienceAustralia/dea-config/tree/master/workspaces no such files in this folder

Run ./setup-db.sh
  ./setup-db.sh
  shell: /usr/bin/bash -e {0}
  env:
    ORG: opendatacube
    IMAGE: wps
    METADATA_CATALOG: https://raw.githubusercontent.com/GeoscienceAustralia/dea-config/master/workspaces/sandbox-metadata.yaml
    PRODUCT_CATALOG: https://raw.githubusercontent.com/GeoscienceAustralia/dea-config/master/workspaces/sandbox-products.csv
Reusing cache..
psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Steps to reproduce the behaviour

start the testing github action

@pindge pindge linked a pull request Dec 2, 2021 that will close this issue
@benjimin
Copy link
Collaborator

benjimin commented Dec 2, 2021

The CI behaviour is also the topic of #137.

Those catalog links are no longer being used (see setup-db.sh) and probably ought be removed now, although the indexer image was still being used (for the tool to index one of the legacy products).

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 a pull request may close this issue.

2 participants