Skip to content
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

Integers defined break ssm-diff #9

Closed
lanmalkieri opened this issue Apr 1, 2019 · 1 comment
Closed

Integers defined break ssm-diff #9

lanmalkieri opened this issue Apr 1, 2019 · 1 comment

Comments

@lanmalkieri
Copy link

It appears that when you define an integer in SSM like

DEBUG_PORT: 80

This breaks ssm-diffs ability to initialize. Example of error output (I also added some print statements in to see where exactly the code was breaking).

NODE_ENV': production, u'TESTS_RUNNING': false, u'DEBUG_PORT': Traceback (most recent call last):
  File "/usr/local/bin/ssm-diff", line 80, in <module>
    args.func(args)
  File "/usr/local/bin/ssm-diff", line 9, in init
    print(r.get(flat=False, paths=args.path))
TypeError: __repr__ returned non-string (type int)

This essentially means that it is not possible to put any integer values into SSM. I can take a stab at fixing this but wanted to raise it as an issue first in the event you guys had a quick/easy fix.

@lanmalkieri
Copy link
Author

Well this is odd, other integers work just fine.

 POSTGRES_PORT: 5432

This initializes without issue.

So after re-creating DEBUG_PORT: 80 as a variable in SSM from scratch, this all worked without issue.

There muse have been some weird case issue with the variable that got created the first time?

Either way I am closing this issue, it appears it was opened in earnest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant