You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
What degrees of freedom do people want to have?
-- 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
Provide architecture guardrails to protect metadata
Security?
Note: Get video link from Miguel C. demo
The text was updated successfully, but these errors were encountered: