luke
luke
Really excited for this feature, let me know how I can help
Hooked up DB changes to scheduler-worker flow.
Unfortunately, publishing to Maven Central is quite a can of worms. Maven Central simply acts as a centralized reverse proxy, and packages synced to Maven Central must actually be hosted...
Looking into this further, I discovered that publishing to Maven Central requires you to have DNS records on the domain these Maven packages are namespaced to e.g. `gov.nasa.jpl.aerie...`, which means...
I've confirmed that we are able to host DNS TXT records under `ammos.nasa.gov`, which will allow us to publish packages under that namespace, e.g. `gov.nasa.ammos.aerie.contrib.*`. This, of course, will require...
Chatted with @jpl-jengelke about publishing under `gov.nasa.ammos.aerie.*`, since AMMOS has already claimed ownership of this top level domain (`gov.nasa.ammos`) with Sonatype (Maven Central publisher). Related to https://github.com/NASA-AMMOS/slim-starterkit-java/pull/5
TODO for this ticket after meeting with Juan: - [ ] GH FN account for Luke - [ ] AWS FN location - [ ] R&TD billing account - [...
Yep, working on them right now using CI tests
@Mythicaeda Ah I didn't push my latest commit with comments / cleanup. Will push when @JoelCourtney is finished force pushing the bug fix
Does the gateway have tests that rely on a live backend?