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

[quest] (implementation) What architecture choices have been made in production deployment? #89

Open
Tracked by #88
cnygardtw opened this issue Apr 13, 2023 · 0 comments
Labels
backstage Backstage working group

Comments

@cnygardtw
Copy link
Contributor

What degrees of freedom do people want to have?

  • Upgrade?
  • Is it central deployment? Or does every domain have it's own instance?
    -- Central instance promotes single source of information
    -- Multiple instances present upgrade issues in terms of consistent versions of core Backstage code

Prefer using standard mechanisms in Backstage

  • augmented YAML with custom properties to support use-case
  • wrote front-end component to search / visualize taxonomy to find item via custom metadata
  • design strategy to keep within the bounds of Backstage product rather than side functionality

Provide architecture guardrails to protect metadata

  • Bot to review / lint yaml
  • restrictions on changing names

Security?

  • Access and entitlements for integrated data

Note: Get video link from Miguel C. demo

@cnygardtw cnygardtw converted this from a draft issue Apr 13, 2023
@ashukla13 ashukla13 added the backstage Backstage working group label Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backstage Backstage working group
Development

No branches or pull requests

2 participants