add actions for CITE testing

[tomkralidis]

Currently, running CITE tests include running against https://cite.opengeospatial.org or running locally via Docker.

For each approved OGC API standard that has an ETS available, we should add a GitHub Action that deploys the ETS Docker image and runs against a pygeoapi configuration for the given ETS

Current OGC API standards with ETSs:

• OGC API - Features
• OGC API - Environmental Data Retrieval
• OGC API - Processes

[ricardogsilva]

@tomkralidis I've started some work on this here:

https://github.com/ricardogsilva/team-engine-action

Still early work, but I'm thinking it would be valuable to contribute it to someplace other than my personal account - perhaps to geopython? or maybe to opengeospatial? I mean after I can get it to a state where it actually works that is 😛

I'm thinking it would be a generic github action, that a user would configure with something like this:

jobs:
  perform-cite-testing:
    uses: team-engine-action@some-version
    with:
      server-url: <URL of the server under test>
      test-suites:
        - <id of ETS 1>
        - <id of ETS 2>
        - ...

[tomkralidis]

Thanks @ricardogsilva. For a broader effort, the best place for this work to take place would be in OSGeo. In the OSGeo Standards Committee we have often discussed the need for shared CITE testing across different OSGeo projects, so this sounds like the opportunity to do so :)

I've created https://github.com/OSGeo/ogc-cite-action and given us admin rights so you can continue the work there. Tagging/inviting @rouault @gfenoy @tfr42 @dstenger @ghobona who may also be interested in this effort.

We can then circle back here to complete integrating the actions the standards in scope.

[mbrachman]

@tomkralidis I'd like chat more about this -- @dstenger and I agree that we should be working more closely with OSGeo. I will send you an email

[github-actions]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

[tomkralidis]

Bumping this issue for status (cc @ricardogsilva)

[github-actions]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.

[mbrachman]

@tomkralidis my apologies for the slow reply on this. bumping this thread again, I will have more bandwidth to synch up with you on this after Innovation Days DC.