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

Agenda for Backstage Community Session (March 16 & 23, 2022) #41

Closed
OrkoHunter opened this issue Feb 24, 2022 · 6 comments
Closed

Agenda for Backstage Community Session (March 16 & 23, 2022) #41

OrkoHunter opened this issue Feb 24, 2022 · 6 comments

Comments

@OrkoHunter
Copy link
Member

Details

  • Date and Time

Day 1 (Adopters)

Day 2 (Contributors)

Wed, March 16th, 16:00 CET (UTC+1)
Use this to convert to your timezone
Wed, March 23rd, 16:00 CET (UTC+1)
Use this to convert to your timezone
Share your adoption challenges and successes, demo features and plugins, and hear about major product updates. Go deeper under the hood — discuss features, implementation questions, and other technical issues with your fellow contributors and the Backstage maintainers.

Zoom details

Join Zoom Meeting
https://spotify.zoom.us/j/99236687098

Note: Please sign up on Zoom if you do not have an account. This meeting requires a Zoom account for joining.

In case you face issues joining - feel free to use the #meetup channel on Discord.

Action Required

  • React with a 👍 - if you intend to join. (RSVP)
  • Add any topic that you think should be discussed as a comment in this issue.
  • You can use [Adopters] or [Contributors] in your comment to label them for a specific track.
  • Upvote existing comments/topics.
@shmaram
Copy link

shmaram commented Mar 9, 2022

Proxy - Should we enable it to all existing http requests? what are the disadvantages, when we should not use it?
is it possible that by allowing all requests to pass through the backstage server we might end up killing the service ? (large data in request , OOM, too many requests in parallel... )

@jrusso1020
Copy link

Proxy - Should we enable it to all existing http requests? what are the disadvantages, when we should not use it?
is it possible that by allowing all requests to pass through the backstage server we might end up killing the service ? (large data in request , OOM, too many requests in parallel... )

There are also security concerns with this approach. If you allow "all" requests to blindly be passed through the proxy plugin a malicious actor could potentially use this to access services/information they should not be able to access normally

@kuangp
Copy link
Member

kuangp commented Mar 17, 2022

I would be willing to do a quick (~5min) demo of backstage/backstage#9841

@julioz
Copy link

julioz commented Mar 18, 2022

I can do a small demo (also 5~10 min) of the Periskop plugin we have open-sourced (backstage/backstage#9816).

@kerberosmansour
Copy link

[Adopters] Interested in learning what other infosec teams have been leveraging backstage to surface security findings to tech teams (both platform and product engineering teams)

@taras
Copy link
Member

taras commented Mar 21, 2022

[Contributors] Frontside team would like to demo the ingestion integration test suite that we created.

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

No branches or pull requests

7 participants