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
  • From the UI
  • From the Data Model Builder
  • From the Blueprint Descriptor
  • From the Public API

Was this helpful?

  1. Software Catalog
  2. Usage Guide

Updating a Blueprint

PreviousCreating a new Blueprint & CatalogNextTracking Blueprint Changes

Last updated 12 months ago

Was this helpful?

From the UI

You can manage your data-model and all its blueprints via:

  • The data model builder for a visual graph-based interface

  • Or by directly manipulating blueprint descriptors.

From the Data Model Builder

The Data Model Builder is the most visually appealing of managing your blueprints, but it's not the most powerful one.

From the builder you are unable to:

  • Edit the blueprint's title.

  • Edit a property's metadata or data-type.

  • Edit a relation's title or overall nature (e.g. its target blueprint or its cardinality between one-to-one and one-to-many).

For these operations, you need to perform updates directly on the blueprint's descriptor.

Changing a blueprint's ID is impossible across the product, regardless of whether via the UI or API. This is a measure meant to prevent issues related to data misalignment.

To see the content of a Blueprint, click on its node in the graph view.

From here, you can create new properties and relations.

From existing relations, you can establish reference properties.

You can also delete existing properties and relations.

Deleting a property or drastically changing its type in the blueprint can cause entities created from it to enter a conflict state that you'll need to resolve manually, see troubleshooting.

You can also edit a blueprint's icon or deleting the blueprint.

Deleting a blueprint can cause other blueprints that have relations to it and its respective entities to enter a conflict state that you'll need to resolve manually, see troubleshooting.

From a blueprint card you can also directly access the blueprint's descriptor for more powerful manipulation capabilities.

From the Blueprint Descriptor

Directly manipulating the blueprint descriptors is the most powerful way of managing your blueprint, but it also requires deeper technical knowledge.

From here, you can customise every aspect regarding your blueprint, like:

  • Editing the blueprint's metadata (except for the ID).

  • Editing properties' metadata and data-type.

  • Editing relations' metadata and overall nature (e.g. its target blueprint or its cardinality between one-to-one and one-to-many).

Some considerations:

Changing a blueprint's ID is impossible across the product, regardless of whether via the UI or API. This is a measure meant to prevent issues related to data misalignment.

Deleting a property or drastically changing its type in the blueprint can cause entities created from it to enter a conflict state that you'll need to resolve manually, see troubleshooting.

Deleting a blueprint can cause other blueprints that have relations to it and its respective entities to enter a conflict state that you'll need to resolve manually, see troubleshooting.

From the Public API

🖥️
Blueprints