Add support for attaching Serverless Containers (and Functions) to Private Networks

[GeryDeKocliko]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Proposal

• What is the proposed change?

Add first-class support in the Serverless Framework plugin (serverless-scaleway-functions) to attach a Serverless Container (and ideally a Function) to one or more Private Networks directly from serverless.yml.
The plugin’s configuration docs show how to define namespaces, functions and containers in serverless.yml, but there is currently no key to specify Private Networks at deploy time. Providing such a key would let users keep networking topology under version control and avoid manual post-deploy steps in the console.
(Refs: plugin README/config section, containers “use Private Networks” doc).

• Who does this proposal help, and why?

Teams running internal services (databases, brokers, APIs) that must be reachable only over VPC/Private Network without exposing extra public egress, and without a separate manual step.
Benefits:
• Security by default: no accidental public connectivity.
• Reproducible infra: PN attachment is declarative in serverless.yml.
• CI/CD friendly: no click-ops between serverless deploy and production.
• Parity with product capabilities (Containers/Functions support PNs per docs).

Example

Below are suggested serverless.yml keys that the plugin could support (names are proposals; exact shape up to maintainers). They mirror how other fields are defined in the plugin today.

service: my-namespace
plugins:
  - serverless-scaleway-functions

provider:
  name: scaleway
  scwRegion: fr-par

containers:
  my-api:
    image: rg.fr-par.scw.cloud/my-reg/my-api:latest
    port: 8080
    # Per-container override
    privateNetworks:
      - id: "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
      # Optional static IP reservation if API supports it
      # - id: "..." 
      #   ip: "10.100.0.42"

functions:
  # (If feasible for Functions too)
  my-func:
    handler: handler.py
    runtime: python310
    privateNetworks:
      - id: "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"

[GeryDeKocliko]

@gueriboutmathieu