aws: changes for unified integration UI#2003
aws: changes for unified integration UI#2003endorama merged 23 commits intoelastic:masterfrom endorama:uniform-ui/aws
Conversation
|
Pinging @elastic/integrations (Team:Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
packages/aws/manifest.yml
Outdated
There was a problem hiding this comment.
Can we replace "from the" with "from" wherever it was provided in the description? Received a review on my spreadsheet that the inconsistency of "the" looks odd.
There was a problem hiding this comment.
@endorama @akshay-saraswat I would suggest keepingCloudTrail, instead of changing it to Cloudtrail. Because in AWS, CloudTrail is the actual service name. For example: https://aws.amazon.com/cloudtrail/
WDYT?
I agree with you. That's my mistake. I did not consider the AWS naming convention while creating the spreadsheet. @endorama please replace |
|
@akshay-saraswat @kaiyan-sheng updated in both places. Just have a look and I'll merge this end of day if there is no more feedback. |
What does this PR do?
Align package title and description for improved Unified Integration UI display.
Checklist
I have reviewed tips for building integrations and this pull request is aligned with them.I have verified that all data streams collect metrics or logs.changelog.ymlfile.manifest.ymlfile to point to the latest Elastic stack release (e.g.^7.13.0).Author's Checklist
How to test this PR locally
Related issues
Screenshots