Allow setting PHP as a runtime in serverless.yml

[mnapoli]

TODO:

• Gather feedback from the community
• Update docs
• Update templates

---

This new feature allows setting PHP as a runtime when deploying with serverless.yml:

service: myapp

provider:
    name: aws

functions:
    function:
        handler: function.php
        runtime: php-81

    api:
        handler: api.php
        runtime: php-81-fpm
        url: true


plugins:
    - ./vendor/bref/bref

This replaces the layers variables (which still work!). One could migrate to this new simpler syntax like this for example:

service: myapp

provider:
    name: aws
-    runtime: provided.al2

functions:
    function:
        handler: function.php
-        layers
-            - ${bref:layer.php-81}
+        runtime: php-81

    api:
        handler: api.php
-        layers
-            - ${bref:layer.php-81-fpm}
+        runtime: php-81-fpm
        url: true

plugins:
    - ./vendor/bref/bref

This removes several wtfs for beginners:

• wtf is "provided.al2"
• wtf are "layers"
• wtf is that ${bref:layer.php-81-fpm} syntax
• wtf do I need 2 layers for console

Regarding the last one, indeed things get simpler for console:

functions:
    console:
        handler: bin/console
-        layers
-            - ${bref:layer.php-81}
-            - ${bref:layer.console}
+        runtime: php-81-console

And also it makes switching to ARM much simpler too because the runtime stays the same, the layer is automatically switched to the ARM layer by the Bref plugin (it detects architecture: arm64):

functions:
    console:
        handler: bin/console
        architecture: arm64
        runtime: php-81 # no need to add the `arm-` prefix

[afu-dev]

Feedback: less things to write = less error possible. Also it feels nicer to read/understand.

Cons: runtime and architecture may be flagged as "error" or "unknown" when using an IDE. Example with PhpStorm

[georgeboot]

Only thing I could really see is that newcomers might also want additional layers (isn't intl going to be a separate layer?) and now you are figuring out why there are 2 ways to declare stuff.

But overall and assuming that this os properly documented, I'm all for!

[mnapoli]

@afu-dev agreed, this is annoying to me as well.

@georgeboot regarding extensions, I was thinking about something like this too:

functions:
    hello:
        handler: ...
        runtime: php-81
        extensions:
            - redis
            - amqp

Would that be better?

(and yes we would need a clear error message in case users hit the layer limit)

[georgeboot]

Would that be better?

Yup amazing!

Could you cook it so that that would also enable the extension? 👀

[mnapoli]

Oh yes definitely!

[mnapoli]

Note: will look into extensions separately.