aws-sam-deploy: Stack name required with package-only command?

[Jared Bates]

We are setting up the aws-sam-deploy pipe and are unsure why a "STACK_NAME" variable is required with the "package-only" command. Because we are doing build-once, deploy-many setup, we don't want to specify a stack name until the deployment of the stack.

Since the "STACK_NAME" variable is not being used at all in the "package-only" command logic, we have simply specified a placeholder variable there, and then are using the "BITBUCKET_DEPLOYMENT_ENVIRONMENT" environment variable to generate the name during the deployment step ("deploy-only" command).

Could the "STACK_NAME" variable not be required with the "package-only" command?

[Halyna Berezovska]

@Jared Bates yes, I see minor issue : sam deploy inherits cloudformation where stack name is required, but if sam does only package, it actually does not use this variable. I see this as a minor issue that you have to specify STACK_NAME variable but it will be never used.

Thanks for reporting,

Galyna