https://serverless-stack.com/ logo
Join Slack
Powered by
I have an old project with Serverless Framework ho...
# seed
g
I have an old project with Serverless Framework hosted on Seed, this morning is getting this error when deploying:
Copy code
Failed
Using Serverless Framework v2.64.1
Learn about how to use a different Serverless Framework version.
Serverless Error: Trying to populate non string value into a string for variable ${deep:0}. Please make sure the value of the property is a string.
Is this Serverless Framework version not more compatible with Seed?
Copy code
Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "custom.ssm.STORAGE_BUCKET_NAME": Value not found at "ssm" source,
              - Cannot resolve variable at "custom.ssm.DEPLOYS_BUCKET_NAME": Value not found at "ssm" source
            From a next major this will be communicated with a thrown error.
            Set "variablesResolutionMode: 20210326" in your service config, to adapt to new behavior now
            More Info: <https://www.serverless.com/framework/docs/deprecations/#NEW_VARIABLES_RESOLVER>
Serverless: [AWS ssm 400 0.04s 0 retries] getParameter({
  Name: '/COSTSHARING/INFRASTRUCTURE/DEPLOYS_BUCKET_NAME',
  WithDecryption: true
})
Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "custom.ssm.STORAGE_BUCKET_NAME": Value not found at "ssm" source,
              - Cannot resolve variable at "custom.ssm.DEPLOYS_BUCKET_NAME": Value not found at "ssm" source
            From a next major this will be communicated with a thrown error.
            Set "variablesResolutionMode: 20210326" in your service config, to adapt to new behavior now
            More Info: <https://www.serverless.com/framework/docs/deprecations/#NEW_VARIABLES_RESOLVER>
These are my dependencies
Copy code
"serverless-bundle": "^3.2.1",
    "serverless-certificate-creator": "^1.4.0",
    "serverless-deployment-bucket": "^1.2.0",
    "serverless-domain-manager": "^5.0.0",
    "serverless-offline": "^6.8.0"
SSM parameters exist I already checked
@Frank sorry I tag you directly but this thing is very strange and potentially could be a Seed bug, basically my AWS IAM Credentials for the stage of my Seed app have been reset. I solved this issue filling again my account credentials. console.seed.run/parque/pulsee-cost-sharing-services It’s very strange, I don’t remember to make some change on credentials since the first setup.
f
Hey @gio, let me take a look at your account.
I pull up your account and it seems the IAM credentials for the 
pulsee-cost-sharing-services
app was updated on Jan 5.
It was set on the entire app (via app settings). ie. the stages inherit the credential from the app if it’s not specified on the stage level.
Earlier today, the credentials for the stages were configured. ie. the stages now no longer inherit the credentials from the app.
The above is what I noticed from the logs on our side. Let me know if that looks right.
g
Thank. you. Frank, I don’t remember to have changed something on app, anyway it’s better was happen this than a problem on Seed. Thank you. so much for support me 🙌
Open in Slack
PreviousNext
Powered by