You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
kombustion upsert ./redshift.yaml --stack-name DataLake-DEV-RedShift --read-parameters ./params.json --region=ap-southeast-2 -i
➜ Generate Default Outputs: [false]
✖ Error: Failed to execute the template
☞ Resolution: File: ./redshift.yaml
template: cfn:123: function "resolve" not defined
✖ Fatal: template: cfn:123: function "resolve" not defined
☞ Resolution: An unknown error occured, please subbmit an issue
∞ More info: https://github.com/KablamoOSS/kombustion/issues/new?template=bug_report.md
Desktop (please complete the following information):
Linux AMD 64 build of v0.5.1
Additional context
Sounds like more custom logic to handle :)
The text was updated successfully, but these errors were encountered:
➜ Generate Default Outputs: [false]
✖ Error: Failed to execute the template
☞ Resolution: File: ./redshift.yaml
template: cfn:134: function "resolve" not defined
✖ Fatal: template: cfn:134: function "resolve" not defined
☞ Resolution: An unknown error occured, please subbmit an issue
∞ More info: https://github.com/KablamoOSS/kombustion/issues/new?template=bug_report.md
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Kombustion fails on inspection of the resolve key word.
Suspect it would also fail on Params Store as well
To Reproduce
Throw the following into and RDS/RedShift properties definition:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Linux AMD 64 build of v0.5.1
Additional context
Sounds like more custom logic to handle :)
The text was updated successfully, but these errors were encountered: