`condition` doesn't affect resources directly associated to resource on which is set

Feature Request

Description

Since #6642, Serverless supports conditional function generation. When a function has http events, the function is conditional but API Gateway resources are always generated (In the generated CloudFormation template, only the “AWS::Lambda::Function” resource has Condition property but “AWS::ApiGateway::Method” resources have not).

functions:
  func1:
    handler: handler1
    condition: IsDevelopment
    events:
      - http: GET hello

resources:
  Conditions:
    IsDevelopment:
      Fn::Equals: [ "${self:provider.stage}", "dev" ]

If a function is conditional, the corresponding http event resources should also be conditional.

Similar or dependent issues:

• #6641 #6642

[medikoo]

@Aposhian I think we may add support for auto assigning the conditions to tightly related resources, but only in case they’re safe

e.g. it’s not safe for API Gateway resources, but it’s safe for e.g. Version or EventSourceMapping resource.

Additionally we may show a log notice if conditions are used with API Gateway, to indicate that those resources cannot be reliably conditioned

PR that implements that in a manner specified here: https://github.com/serverless/serverless/issues/7070#issuecomment-630721129 is definitely welcome

[zoellner]

For those coming here and looking for a solution while this issue isn’t fixed: I ran into the same issue and found https://www.serverless.com/plugins/serverless-plugin-conditional-functions to be an easy workaround for now.