Repository navigation
Conversation
The params are forwarded as-is to osls, on both `serverless deploy` and the
`serverless info` that follows it, so that `${param:...}` variables resolve
in both. bref.php applications reject the option.
Claude-Session: https://claude.ai/code/session_01Y4Gb7wKthAh4iXemSDps7M
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bref deploy --param="key=value"(repeatable) passes Serverless Framework parameters to aserverless.ymlapplication, likeserverless deploy --param.serverless deployand on theserverless infothat follows it (otherwise a${param:...}without a default would fail there, after a successful deployment).Checked locally that osls@3 accepts
--paramondeployandinfo, and resolves--param <value>passed as a separate argument (osls print, including a value that contains=). Not tested against Bref Cloud.