sls4's bug during 5/2~5/7's changed

[gavinsui1106]

when i used the command serverless deploy --stage ${env} in sls3 . it always worked!
when i use the command in sls4 first time (2024/5/2) it also worked! but when i use the command after a few days (2024/5/7), it failed!
i dont konw what happend in thoes days, anyone can tell me why ? and how to change my sourcecode? here is the whole error message and my sourcecode.

error message
Failed to resolve variable 'custom.${opt:stage' with resolver 'config' :ERROR :Key "custom.${opt:stage" is not defined in config file.

buildspec.yml

serverless deploy --stage ${env}
#${env} is set with environment during AWS's Coodebuild . for example ,Dev is the value of env.

serverless.yml

provider:
  name: test
  runtime: dotnet6
  region: XXX
  environment: ${file(slsconf/serverless_environment.yml)}
  role: arn:aws:iam::${self:custom.${opt:stage, self:provider.stage}.EnvironmentVariable1Val}:/role/${self:custom.${opt:stage, self:provider.stage}.EnvironmentVariable2Val}

custom:
   ${file(slsconf/serverless_custom${opt: stage, self: provider.stage}.yml)}

slsconf/serverless_environment.yml

TZ: XXX
EnvironmentVariable1: ${self: custom.${opt: stage, self: provider.stage}.EnvironmentVariable1Val}
EnvironmentVariable2: ${self: custom.${opt: stage, self: provider.stage}.EnvironmentVariable2Val}

slsconf/serverless_customDev.yml

EnvironmentVariable1Val: XXX
EnvironmentVariable2Val: XXX

[gavinsui1106]

@serverless-ci @ServerlessBot
pls

[gavinsui1106]

@ServerlessBot @serverless-ci

when i used 4.0.30(release date is 2024/5/27)
another error is happened .
maybe this is a bug.
error message:

s:core:meta: saving meta record to global .serverless directory. s:cli-error-handler: currentValue.replace is not a function TypeError: currentValue.replace is not a function at #replacePlaceholderInConfig (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:24501) at #handlePlaceholderNode (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:20573) at async file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:18650 at async processNodeAndHandleCompletion (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:13936)
✖ currentValue.replace is not a function TypeError: currentValue.replace is not a function at #replacePlaceholderInConfig (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:24501) at #handlePlaceholderNode (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:20573) at async file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:18650 at async processNodeAndHandleCompletion (file:///root/.serverless/releases/4.0.30/package/dist/sf-core.js:1041:13936)

[czubocha]

Hi @gavinsui1106, unfortunately, I am unable to reproduce the error with the config you provided in the original comment. To assist you better, could you please provide an example configuration that reproduces the error? This will help us identify the issue more accurately and provide a solution.

[czubocha]

Hello @gavinsui1106,

Thank you for bringing this to our attention. We're aware of the issue you've encountered with variable resolution in Serverless Framework v4, and we're actively working on a fix that will be included in the next release.

In the meantime, you might consider simplifying your approach to managing parameters and stage configurations. Here are a few alternatives that could help:

• Using Parameters: Define all necessary parameters directly within your configuration files. More details can be found in our guide on using parameters with Serverless Framework.

• Environment Variables: You can use .env files to define your variables, which is now enabled by default in v4. For further information, please check out our documentation on environment variables.

• External Secrets Management: For a more secure approach, consider using the Serverless Dashboard or AWS SSM for secrets management. These methods provide secure storage and access to your parameters. More on this can be found here:

  • Dashboard Parameters
  • AWS SSM with Serverless Framework.

I'm curious about the specific requirements that led to the complex configuration you've implemented. Understanding your specific needs can help us provide better guidance and improve how the framework handles such configurations. Could you share more about why this approach was chosen?

[gavinsui1106]

hi@czubocha ,
thank you for your answer ,
waiting for the next version !
by the way ,in the command [serverless deploy --params=""],params can no longer be used too,pay attention pls