Install COG Plugin on Docker

All very good points but the truth is people are using it in production deployments.

Which makes me think:

  • We could add some sort of unsupported flag to ModuleInfo and present a warning in the UI for those modules.
  • COG’s become so important that it’d deserve a small code sprint for promotion as extension. Afaik the estimate for upgrading the COG plugins with the crowdfunding funds only covers Java17/JakartaEE upgrades, not promotion to extension.

thoughts?

Yes, community modules are often used in production and they often work fine under selected use cases, but they are not ready for general consumption.
Just thinking about what else might not be working in the COG modules, is that they are not tested under the many ways one can authenticate in the cloud. Maybe they work, maybe they have been manually tested once, but we don’t know fur sure, especially across library upgrades.
Given the cloud libraries have a lot of dependencies, packaging tests play also an important role, but right now we don’t have any test checking if the zip working at all (if often happens that it works in the IDE but not when deployed).

I’d be very much in favour of having this in addition to having these modules available only through nighly builds.

Yes please! Funding to make these modules get graduated is indeed all that’s missing. Right now we need to concentrate on GeoServer 3, but I would not mind

Cheers
Andrea

Hello @fernandoquadro , I got it installed, but I had to build a new image of GeoServer with the plugin alrerady installed. It got installed but it didn’t worked very well. Long history short, I’ve switched over to the S3 plugin, which has basically the same features as the COG.

1 Like

By the way, this has been fixed in the meantime, along with some packaging issues for Azure. The other tasks are still needed, looking for coders or sponsors to take on them.

Cheers
Andrea