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

Create SSM secret automatically - partially solve #389 #418

Closed
wants to merge 1 commit into from

Conversation

hugosenari
Copy link
Contributor

@hugosenari hugosenari commented Nov 22, 2019

#389 - Ease the run of manual acceptance tests:

  • Create SSM secret automatically.

- SSM secret is not created automatically.
@hugosenari hugosenari requested a review from ceilfors November 22, 2019 19:47
@hugosenari hugosenari changed the title laconia#389 - Ease the run of manual acceptance tests Created SSM secret automatically - partially solve #389 Nov 22, 2019
@hugosenari hugosenari changed the title Created SSM secret automatically - partially solve #389 Create SSM secret automatically - partially solve #389 Nov 22, 2019
Copy link
Collaborator

@ceilfors ceilfors left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR! Feel free to merge!

I realise that this is not a SecretString, but it is still probably worth making this automated, as there's already a test that covers this via unit test should hit SSM with Decryption option.

@hugosenari
Copy link
Contributor Author

hugosenari commented Nov 25, 2019

Sadly, CloudFormation doesn't support creating a SecureString parameter type.

Anyway with this, at least we test that Laconia/Config reads information from SSM. :-)

ceilfors added a commit that referenced this pull request Dec 3, 2019
The parameter is being created in acceptance.spec.js because CloudFormation does not support SecretString creation, obviously due to security reason.
In our case, as this is not really a secret, it is safe for us to have the plain text secret in our test.

This closes #418
Copy link
Collaborator

@ceilfors ceilfors left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @hugosenari. I have another PR that will close this PR: #432. Let me know what you think!

@hugosenari
Copy link
Contributor Author

close this in favor of PR: #432

@hugosenari hugosenari closed this Dec 4, 2019
@hugosenari hugosenari deleted the laconia-#389 branch December 4, 2019 18:29
hugosenari pushed a commit to hugosenari/laconia that referenced this pull request Dec 4, 2019
The parameter is being created in acceptance.spec.js because CloudFormation does not support SecretString creation, obviously due to security reason.
In our case, as this is not really a secret, it is safe for us to have the plain text secret in our test.

This closes nearst#418
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

Successfully merging this pull request may close these issues.

2 participants