apiman

Open Source API Management

[Marc Savy @marcsavy]

Apiman https://t.co/ZTqn5ZqOQ8 is released — a few useful features, bug fixes, and remedies a CVE. See more here: https://t.co/ZWNyZd266N

[Marc Savy @marcsavy]

Apiman Quarkus distribution (OpenJDK not native)?

[apiman @apiman_io]

Please read about Apiman CVE-2022-47551, a potential permissions bypass vulnerability, to see whether you need to take action to upgrade.

https://t.co/kc58sLLEns

[apiman @apiman_io]

If you had issues starting the Apiman 3 docker-compose distro, please re-download. A config fix was not pushed before the release.

[Marc Savy @marcsavy]

A key feature I implemented in Apiman 3 is a flexible event subsystem underpinned by a transactional outbox — this lets external consumers subscribe to Apiman's events via platforms like Kafka (API signups, API approval requests, etc).

Blog:

https://t.co/Z78KsjwmXg

[Marc Savy @marcsavy]

I'm delighted to say that Apiman 3 is officially released! Lots of new features and behind-the-scenes improvements

I've also painstakingly overhauled the Apiman website and docs from ground up

Also a new Docker Compose distro — it's easy to get started!

https://t.co/FZumfUwVab

[Marc Savy @marcsavy]

Trying to get a significantly updated GitHub Actions release pipeline working for the first time.

How many release candidates will I need before the whole thing works?

Will it be over 9000?

[Marc Savy @marcsavy]

Been slaving away on the new Apiman @apiman_io website for a good while, with all the automation improvements.

Not far away from finished.

Then I can finally cut the Apiman https://t.co/2r1ZZjCb5j release 😅.

#OneManBand

[Marc Savy @marcsavy]

In Apiman 3 we are using @jbangdev to automate the generation of some secrets and keys for our Docker Compose quickstart 🚀.

https://t.co/R4f2kFozRc

[Marc Savy @marcsavy]

Open source community chat... Zulip or Discord?

[apiman @apiman_io]

Is anyone interested in @diagridio dapr support for Apiman?

Thread here: https://t.co/giAkswTk0l

[Marc Savy @marcsavy]

Another day of (almost) 100% docs on Apiman 3 @apiman_io 😮‍💨.

[apiman @apiman_io]

For Apiman 3 I'm very pleased to say we are using @c_beikov's Blaze-Persistence as a replacement for the JPA Criteria API.

Blaze-Persistence can be understood by mere humans, like Apiman's maintainer!

https://t.co/uNgSr2LyUy

[apiman @apiman_io]

Apiman himself appears in version 3 of the docs with the occasional message from the developers 🦸‍♂️

[Marc Savy @marcsavy]

Been slaving away all week on Apiman https://t.co/2r1ZZjBDfL documentation. Still at it.

[apiman @apiman_io]

@marcsavy It'll be very easy to get started, even if you have very little patience.

[apiman @apiman_io]

Apiman docker-compose distro for https://t.co/MqfUDuvZHu nearly ready 🚀. Exciting times!

This will be the main Apiman Quickstart distro from https://t.co/MqfUDuvZHu onwards.

Marc Savy (@marcsavy) has been working/sweating/tearing hair out on this 😅.

[apiman @apiman_io]

Is anyone interested in support for QuestDB with Apiman Metrics?

https://t.co/eCXSWVk45J

[apiman @apiman_io]

IPv6 support added for blacklist/blocklist and whitelist/allowlist for Apiman 3 -- oh, and now you can use CIDR and dashed ranges 😎.

[@marcsavy worked on this]

[apiman @apiman_io]

Our new implicit permissions system implementation has landed on 3.x branch (we call it 'discoverability')

You can now expose APIs to consumers who are not members of your organisation. Even to anonymous browsers in the developer portal, if you want

https://t.co/nHK7wRtJf0