-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cleanup branch #115
Cleanup branch #115
Conversation
…cloudformation bugs
Description: > | ||
Elastic Serverless Forwarder | ||
|
||
SAM Template for the macro, not intended to be deployed on its own |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ravikesarwani
please, let me know if you want to improve the wording of this sentence in order to instruct the users that this specific application is not the one to be deployed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's my suggestion around naming the helper macro and the application.
Macro:
Name: helper-macro-elastic-serverless-forwarder
Description:
NOTE: DO NOT DEPLOY
Deploy elastic-serverless-forwarder instead. This is a helper SAM template for the macro and not intended to be deployed on its own.
Application:
Name: helper-application-elastic-serverless-forwarder
Description:
NOTE: DO NOT DEPLOY
Deploy elastic-serverless-forwarder instead. This is a helper SAM template for the application and not intended to be deployed on its own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will replace the content, but links are not available in the SAR snippet.
Please let me know if you prefer
Deploy elastic-serverless-forwarder instead.
or
Deploy https://serverlessrepo.aws.amazon.com/applications/eu-central-1/267093732750/elastic-serverless-forwarder instead.
(I would rather use the link to the app in SAR, the one you've provided is region specific)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Deploy elastic-serverless-forwarder instead." is fine.
🌐 Coverage report
|
@@ -290,6 +290,11 @@ def add_output(self, output_type: str, **kwargs: Any) -> None: | |||
|
|||
output: Optional[Output] = None | |||
if output_type == "elasticsearch": | |||
if "es_index_or_datastream_name" in kwargs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we link to an issue where this breaking change is detailed and is written the action item of removing this check at a later version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
share/config.py
Outdated
@@ -57,7 +57,7 @@ def __init__( | |||
self.username = username | |||
self.password = password | |||
self.api_key = api_key | |||
self.es_index_or_datastream_name = es_index_or_datastream_name | |||
self.datastream = datastream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Albeit this is called datastream
can still receive an index name, is that correct? So the functionality is still there, we just renamed the setting field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we put the current image from SAR showing the 3 apps as will be seen by the customers? |
I cannot take the screenshot from SAR before we actually deploy the application. This is a screenshot of my dev deployment (note my name as author): Not sure about the order the three application areshowed: it seems to be the publication order (first macro helper, then application helper, then the main bundled one), but I remember having seen different order while developing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Cleanup
What does this PR do?
Add CF params to easy deploying through IaC
Replace
es_index_or_datastream_name
in elasticsearch output withdatastream
Why is it important?
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areasCHANGELOG.md
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs