Private endpoints

[itowlson]

The proposed syntax is that a private endpoint still requires a [[trigger.http]], but has route = false instead of an actual route pattern. (This creates the slight idiosyncrasy that route = false is allowed but route = true is not. I can live with this!)

In addition to unit tests, the front-to-back service chaining test is modified to make the middle component a private endpoint. Let me know if you think further tests are needed or if they should be reorganised to be more specific.

[fibonacci1729]

This looks great to me. I can live with the route = true weirdness too.

Another possible way to express this which we can absolutely ignore that i mentioned if the hate is too strong:

[[trigger.http]]
 # public defaults to `true` to retain `route = "/..."` syntax
route = { path = "/...", public = false }

This has the added benefit of allowing private endpoints to express a route prefix. Admittedly i can't come up with a use-case for this.

Just tossing out low-blood sugar ideas.

[ThorstenHans]

This is great!

Although it is already merged, I would also prefer using a property that reflects visibility as suggested by @fibonacci1729

Some additional ideas:

• private = true
• internal = true
• public = false