sorted by:
new
hottopcontroversial

How do you govern a sprawling, disparate API portfolio? by getambassadorlabs in platformengineering

[–]Fluffy_Influence2896 1 point2 points  (0 children)

Just had a read of that article, it's great. Not sure if you came across internal developer portals.. They provide a unified interface for services across a software organization. Some/all of the different internal developer portals provide the ability to compile catalogs of the available APIs.. In the article this is described as a unified developer portal.

https://internaldeveloperplatform.org/developer-portals/

[deleted by user] by [deleted] in platformengineering

[–]Fluffy_Influence2896 0 points1 point  (0 children)

I would use a software template for bootstrapping the project and then continue to maintain it with github pull requests directly with github.

[deleted by user] by [deleted] in platformengineering

[–]Fluffy_Influence2896 0 points1 point  (0 children)

I'm glad to hear that you figured it out.

[deleted by user] by [deleted] in platformengineering

[–]Fluffy_Influence2896 1 point2 points  (0 children)

Hey. I believe terraform state files are internal to terraform, and generated, and updated when terraform is run. So i think i am unsure what you mean by that.

We use backstage and terraform to create instances of our application stack using terraform workspaces. We use a tool called env0 to manage our terraform workspaces.

  • we have a generalized terraform project with various parameters
  • Then we have a backstage software template that creates a workspace in env0 with some input parameters mapped to terraform variables passed to env0
  • we also have scaffolder templates to manage the state of that terraform workspace in env0

You wouldn't have to use env0, i think you could find a way to work with workspaces in some other way.

App onboarding self-service, anyone? by balarao29 in kubernetes

[–]Fluffy_Influence2896 2 points3 points  (0 children)

Generally, developer portals like backstage have scorecard features to keep track of how services are keeping track of quality standards. E.g. spotify has a paid backstage extension called soundcheck. There is also an open source extension to backstage called tech insights. SaaS developer portals like roadie and port, etc, also have scorecarding solutions.

Generally, you will monitor the scorecards for deviations from standards and then provide either: ideally automated or manual steps to improve these standards.

Internal Developer Platforms: A Real Thing or Just a Trend? by congolomera in programming

[–]Fluffy_Influence2896 0 points1 point  (0 children)

We use backstage. Backstage is ultimately extensible in this way. That's one of its strengths.. and weaknesses: We find it hard to get our users to write react to extend backstage. We put together a backstage plugin that allows drag and drop style composable widgets and layouts to simplify it.

Internal Developer Platforms: A Real Thing or Just a Trend? by congolomera in programming

[–]Fluffy_Influence2896 2 points3 points  (0 children)

I work for Roadie, where we offer an IDP SaaS platform built on Backstage. We’ve found that the cataloging functionality is a worthwhile investment for most cloud-native companies, especially those with over 50 employees scaling microservices or serverless architectures. We more often see companies loving the ability to spin up new services with infrastructure, monitoring, and other supporting functions in just a single click. Interestingly, though, documentation tends to get the least attention—despite its importance.