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

support for multiple pulumi stacks or entire projects in backstage component #27

Open
krisdock opened this issue Apr 15, 2024 · 1 comment
Assignees

Comments

@krisdock
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

currently, the pulumi-backstage-plugin is limited to displaying information about a single pulumi stack within a backstage component. while this is useful, there are scenarios where users may need to view multiple stacks or even an entire pulumi project within a single backstage component.

feature request:
to enhance the flexibility and usability of the pulumi-backstage-plugin, i propose the following feature:

  1. allow users to configure multiple pulumi stacks within a single backstage component. this would enable users to view and manage multiple stacks simultaneously, providing a more comprehensive overview of their infrastructure.

  2. alternatively or additionally, provide the ability to pull in an entire pulumi project and display a dropdown menu allowing users to select a specific stack within that project. this would give users the flexibility to navigate between different stacks within a project directly from the backstage component.

use case:

  • users who manage multiple pulumi stacks for different environments (e.g., development, staging, production) or regions (e.g., us-east-1, us-west-2) within a single project would benefit from being able to view these stacks within a single backstage component.
  • organizations with complex infrastructure setups spanning multiple projects and stacks would find it more convenient to access their pulumi resources from a centralized location in backstage.

i believe this feature would greatly enhance the functionality and user experience of the pulumi-backstage-plugin, making it even more valuable for users leveraging pulumi within the backstage ecosystem.

please let me know if you have any questions or require further clarification.

@dirien dirien self-assigned this Apr 15, 2024
@dirien
Copy link
Collaborator

dirien commented Apr 15, 2024

Hey @krisdock,

thanks for the feedback! 🙌 Let me have look into your features and break them down into some actionable items.

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

No branches or pull requests

2 participants