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

Instead of blacklisting chars in the resource name for cloudformation use whitelisting. #10087

Merged
merged 3 commits into from Jan 16, 2019

Conversation

ph
Copy link
Contributor

@ph ph commented Jan 15, 2019

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420

@ph ph requested a review from kvch January 15, 2019 17:03
@ph ph added the needs_backport PR is waiting to be backported to other branches. label Jan 15, 2019
@ph
Copy link
Contributor Author

ph commented Jan 15, 2019

@kvch This should solve the issue with the wrong log group, I haven't been able to reproduce the other bug yet.

@kvch
Copy link
Contributor

kvch commented Jan 16, 2019

The failing tests are fixed on master. A rebase should correct the errors.

@ph ph force-pushed the fn/correctly-normalize-log-group branch from 8857c4d to 49ab398 Compare January 16, 2019 16:03
@ph
Copy link
Contributor Author

ph commented Jan 16, 2019

rebased and pushed.

@ph
Copy link
Contributor Author

ph commented Jan 16, 2019

errors are not related to this change.

@ph ph merged commit 56c6857 into elastic:master Jan 16, 2019
@ph ph added v6.7.0 and removed needs_backport PR is waiting to be backported to other branches. labels Jan 16, 2019
ph added a commit to ph/beats that referenced this pull request Jan 16, 2019
… use whitelisting. (elastic#10087)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
(cherry picked from commit 56c6857)
@ph ph added the v6.6.0 label Jan 16, 2019
ph added a commit to ph/beats that referenced this pull request Jan 18, 2019
… use whitelisting. (elastic#10087)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
(cherry picked from commit 56c6857)
ph added a commit that referenced this pull request Jan 21, 2019
… use whitelisting. (#10087) (#10120)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420
(cherry picked from commit 56c6857)
ph added a commit that referenced this pull request Jan 21, 2019
…rce name for cloudformation use whitelisting. (#10121)

Cherry-pick of PR #10087 to 6.6 branch. Original message: 

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…e resource name for cloudformation use whitelisting. (elastic#10121)

Cherry-pick of PR elastic#10087 to 6.6 branch. Original message: 

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants