Rely.io
  • πŸ“ŒWhat is Rely.io?
  • πŸ’‘How Rely.io works
  • πŸ“‘Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • πŸ“šGuides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • πŸ–₯️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • πŸ₯‡Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚑Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • πŸ€–Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • πŸ”ŒPlugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • βš™οΈInvite Users
  • πŸ›‘οΈSecurity & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • πŸ₯Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page
  • Integration with Your Engineering Stack
  • Behind-the-Scenes

Was this helpful?

  1. Plugins & Automation

What happens when you install a Plugin?

PreviousPlugins & AutomationNextSelf-Hosting Plugins using Galaxy

Last updated 6 months ago

Was this helpful?

Integration with Your Engineering Stack

Rely.io seamlessly integrates with your engineering stack through plugins, each enhancing the platform with specific functionalities. Begin your Rely.io journey by using these plugins to populate your software catalog with services, cloud resources, and more.

For instructions on how to setup your first plugin check our guide for a basic starting point, however if you want to know further check and the .

If you are curious about what happens under-the-hood when installing a plugin continue reading.

Behind-the-Scenes

  • Data Model Expansion: Installing a plugin triggers an expansion of your within . This expanded model can accurately represent and display entities related to the plugin's data source.

  • Mass Discovery Run: Post-setup, Rely.io initiates a mass discovery run to query the data source, ingesting entities based on the assets you selected. This ensures your Rely.io catalog mirrors the external data source accurately.

  • Synchronization: Rely uses webhooks for real-time updates from your data sources, ensuring your catalog is up-to-date. For plugins without webhook support, Rely.io schedules periodic discovery runs to keep your catalog synchronized.

  • Automation Rules: Once a plugin is installed, automatically creates automation rules to link, map, and auto-populate your key assets (like services and resources) based on the data provided by the plugin’s data source.

    • For example, installing a Git provider plugin means repositories identified during the discovery phase will automatically create service entities in your catalog.

    • These entities will be enriched with vital information such as the code languages, repository links, README content, etc.

    • As more plugins are installed and more automation rules created, your catalog becomes more detailed enhancing your understanding and management of your tech ecosystem.

↗️
getting started
self-hosting a plugin
plugins installations guides
data model
Rely.io
Rely.io