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
  • Common Issues When Creating and Updating Entities
  • Entity IDs
  • Property Values
  • Relations
  • Common Issues When Creating and Updating Blueprints
  • Blueprint IDs
  • Reach Out to Customer Support

Was this helpful?

  1. Software Catalog

Troubleshooting

Common Issues When Creating and Updating Entities

Entity IDs

  • Format Requirements: Entity IDs must be in lowercase and should not contain special characters.

  • Immutability: Once an entity ID is created, it cannot be updated. If a change is necessary, the entity must be recreated with the desired ID.

  • Uniqueness: Each entity ID must be unique across all entities within the catalog to prevent identification errors.

Property Values

  • Data Type Compliance: Property values must match the data type specified in the blueprint. The system performs validations on these values to ensure they adhere to the defined type and format arguments in the blueprint.

  • Non-nullable Values: Property values cannot be set to null. If you need to remove a property value, you should delete the entire key-value pair from the entity descriptor.

Relations

  • Relation Types: Relations in a blueprint are defined as either 1:1 or 1:many. In the entity descriptor, this is reflected by setting relation values to either a single entity ID or a list of entity IDs.

  • Invalid States: If drastic changes are made to a blueprint (e.g., removing properties or relations that are already utilized in entities), your entity might enter an invalid state. It’s required to update all related entities to align with the new blueprint structure to maintain system integrity.

If you need to propagate changes to several entities in you software catalog, feel free to leverage the python script provided bellow.

Common Issues When Creating and Updating Blueprints

Blueprint IDs

  • Format Requirements: Blueprint IDs must be lowercase and devoid of special characters to maintain system consistency.

  • Immutability: Blueprint IDs cannot be updated after creation. To modify an ID, a new blueprint must be created with the correct ID, and the old blueprint must be deprecated.

  • Uniqueness: Each blueprint ID must be unique across all blueprints to ensure accurate references and dependencies within the catalog.

Reach Out to Customer Support

If you encounter any issues that you're unable to resolve on your own, please don't hesitate to contact our support team at support@rely.io.

PreviousRelevant GuidesNextScorecards

Last updated 11 months ago

Was this helpful?

Additionally, if you would like to discuss a specific use-case you're targeting, feel free to to brainstorm and gain further insights.

πŸ–₯️
book a session with one of our experts