Skip to content

Allow images from the elastic-severless-forwarder repo #1140

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

Merged
merged 2 commits into from
Apr 16, 2025

Conversation

colleenmcginnis
Copy link
Contributor

Related: elastic/elastic-serverless-forwarder#879

I'm not sure why this line was added, but I was unable to get images to appear in my local versions of https://www.elastic.co/docs/reference/aws-forwarder and https://www.elastic.co/docs/reference/aws-forwarder/aws-deploy-elastic-serverless-forwarder until I removed this line.

@Mpdreamz
Copy link
Member

I think I added it becAuse all the images at the root were throwing up errors.

https://github.com/elastic/elastic-serverless-forwarder/tree/main/docs

Will need to double check again if it's not fixed since.

@colleenmcginnis
Copy link
Contributor Author

I deleted the images at the root in elastic/elastic-serverless-forwarder#879. If needed, we can merge that PR first.

@colleenmcginnis
Copy link
Contributor Author

I deleted the images at the root in elastic/elastic-serverless-forwarder#879. If needed, we can merge that PR first.

Ok. It looks like I do need to merge elastic/elastic-serverless-forwarder#879 before this. Let me work on getting an approval.

Copy link

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

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

LGTM! 🦘

@colleenmcginnis colleenmcginnis merged commit 405cc60 into main Apr 16, 2025
14 of 15 checks passed
@colleenmcginnis colleenmcginnis deleted the allow-esf-images branch April 16, 2025 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants