Open chkrause opened 2 years ago
Thanks for opening this. At the moment (as you experienced) it's not possible with Compose to pass parameters with CLI options, or define stage parameters in YAML config.
It's probably something we want to support eventually though, so let's keep this issue open 👍
The issue is that you can not longer use serverless package --service service-b
as a result because params would be undefined is not passed from another service.
Could you clarify @semiautomatixfu? The params should still be passed, but --param
CLI option is not supported on Compose level
@pgrzesik I'm referencing this issue https://github.com/serverless/compose/issues/148
is there any major blocker here just supporting passthrough for cli args that aren't supported 1st class by compose? it seems that the additional comments raised that cause concern are more about specialised usage of compose, I'd simply like to define core env variables to provide consistently across deployment during a CD pipeline.
Any update on this feature request ?
Hello any update on this feature?
Hi @mnapoli , is anyone looking at this feature?
Yes - it will be very usefull
Maybe you know workarounds to pass params on deploy? Because do not wont to hard code it in serverless.yml
@akordzik I no longer work at Serverless Inc. so I cannot answer that.
Unfortunatly I can't pass param to the serverless compose.
serverless deploy --stage del --param="AccountIdZendesk=xxxxxxx"
Cannot resolve variable at "custom.AccountIdZendesk": The param "AccountIdZendesk" cannot be resolved from CLI options or stage params. If you are using Serverless Framework Compose, make sure to run commands via Compose so that all parameters can be resolved
The "--param" option is not supported (yet) in Serverless Framework Compose
I have currently 2 serverless projects depending on each other. One of the projects requires a parameter that has to be defined at deployment time.