DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Security Is a Platform Property, Not a Pipeline Step
  • An XGBoost Property Valuation Postmortem: Leakage, Overfitting, and SHAP Surprises
  • Comprehensive Guide to Property-Based Testing in Go: Principles and Implementation
  • Implement Hibernate Second-Level Cache With NCache

Trending

  • Closing the Drift Loop: An AI Agent That Drafts Terraform Fixes
  • Applying Microservices Lessons to Multi-Agent AI Systems
  • Why Kotlin or Java Is the Wrong Question For Enterprises
  • When RabbitMQ Accepts a Message but Does Not Route It to a Queue

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

uDeploy Built-in Properties Run-Down

By 
Eric Minick
·
May. 13, 12 · Interview
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
12.7K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

A few folks suggested to me that a bit more information on the built-in properties and property scoping for uDeploy would be handy. Message received, and we’ll flesh out the documentation on that front. In the meantime, here’s a quick list of the automaticly available properties.

${p:version.name}

${p:version.id}

${p:component.name}

${p:component.id}

${p:resource.name}

${p:resource.id}

${p:application.name}

${p:application.id}

${p:environment.name}

${p:environment.id}

${p:<property name>} – Process properties. Defined on the process’s “properties” tab, given values by whoever is running the process.

${p:component/<property name>} – Component custom properties, set on the component’s “properties” tab.

${p:environment/<property name>} – Environment properties. These come from two places. You can define properties on the component’s properties tab, under the Environment Properties table. You then give values for these on each environment using the component. In addition, you can set custom environment properties on the environment’s properties tab. These custom properties will override the properties coming from components, although it’s recommended to avoid having the same name in both places.

${p:resource/<property name>} – Resource properties. This can include the built-in agent properties as well as any custom properties. Each of these have their own tab on the resource.

${p:resource/<role name>/<property name>} – Resource role properties. These are defined on resource roles, and the values are set when you add a role to a resource.

${p:application/<property name} – Application custom properties. These are set on the application’s properties tab.

${p:system/<property name>} – Global system properties. These are set on the “System Properties” page in the Settings area.

All of the following are comma-separated series of name=value, including each property on the given object.

${p:component/allProperties}

${p:environment/allProperties}

${p:resource/allProperties}

${p:system/allProperties}

Property (programming)

Published at DZone with permission of Eric Minick. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Security Is a Platform Property, Not a Pipeline Step
  • An XGBoost Property Valuation Postmortem: Leakage, Overfitting, and SHAP Surprises
  • Comprehensive Guide to Property-Based Testing in Go: Principles and Implementation
  • Implement Hibernate Second-Level Cache With NCache

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook