Erik Erikson

Attempting to summarize... A provider knows how to manage asset access according to its own schemes but not all others and vice versa. Regardless of the possibility of writing authentication...

I was intentionally obtuse. Consider a JWT. I imagine that they might contain a credential along with identifying information for the scope on the respective side and anything else, possibly...

The string "B/1" would be satisfactory "materials". It is generated by B and used by B after passing through the custody of A. What you describe is implied authorization for...

Seems more straightforward for A to dispense materials that can be handed to B (to hand back to A) for channel establishment. Why not do that?

Sorry, no opinion in particular. It's not clear to me that json-ref will deal with unparsed yaml. That module was originally introduced in order to help deal with circular references...

I won't be responding fully just now (I'm on vacation) but I think it would be helpful to be absolutely crisp about the use case you're trying to enable. Is...

Following up here... `js-yaml` supports the merge operator. however, in your case you want it to merge the object that would result from replacing not yet rendered variable. yaml parsing/resolution...

@simonbuchan thanks for sharing your knowledge! Interesting option that I was ignorant of but find interesting. This could imply ceding some UX control and potentially break custom formats or the...

BTW, a work around here is to move your STAGE and REGION into the `config/${self:provider.stage}.yml` file. They can continue to be defined as given and will be rendered in the...

@thomasmichaelwallace provided an interesting option elsewhere: >we do the equivalent of `cat serverless.common.yml serverless.project.yml > serverless.yml && serverless deploy` > >You can then use yaml anchors to pull in bits...