apis

• Projects based on Blockchain Technology other than Cryptocurrencies should be added to the Blockchain Category
• Projects which uses blockchain technology and are Cryptocurrencies should be added to the Cryptocurrency category only and not to the Blockchain category.
• No API should be added to both the categories. If it's crypto then add it to cryptocurrency if it's not and uses blockchain te

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

Present in WireMock 2.31.0.

e.g. /__admin/requests?since=2021-09-10T11222:11:10Z causes an exception to be thrown (and thus 500 returned).

Should return a 400 with some context.

Summary

We currently don't good import rules for this. It would simplify readability if these were standardised.

Discord Message
Whilst Pipedream can trigger actions on Discord, there is no simple way for Discord users to communicate with the Discord bot, triggering Pipedream workflows.

Triggers which would assist with this include:

• Listening for direct messages from users to the bot
• and / or listening in a specified channel for a specific command string (eg: !runprocess) [Slash commands?](htt

A Kong SNI can only point to a single certificate. Per Kong/kubernetes-ingress-controller#1268 (comment), misconfigured Kubernetes resources can attempt to point an SNI to multiple certificates.

While we do avoid adding attached SNIs to new certificates, we do

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir