-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template file without parameters fails in v2 #51
Comments
One of the properties parameter_files or parameters is required for the pipeline to generate an event with the parameters for the state machine. Please give a thumbs up this comment if this feature is applicable to you. Thanks. |
We should have the ability to deploy templates using only the default values contained within. |
Not only that, but we currently have a stack in our manifest that has no parameters, so we'll have to add one just to get it to deploy. We just went through an exercise to leverage SSM for organization specific parameters so that we can deploy the same customizations package to multiple organizations, and since most of our parameters were organization related, we are increasingly using fewer parameters in the stacks. |
Updating the manifest version to 2021-03-15 seemed to solve this for us. |
Thanks @cabjas01 for confirming. |
The resource.paramter_file is passing Null value when there is no parameter file for a given template. The
manifest.yaml
is inherited from version 1 repo.This forces the template files to have a parameter.
The text was updated successfully, but these errors were encountered: