27 lines
1.3 KiB
YAML
27 lines
1.3 KiB
YAML
# Use this changelog template to create an entry for release notes.
|
|
#
|
|
# If your change doesn't affect end users you should instead start
|
|
# your pull request title with [chore] or use the "Skip Changelog" label.
|
|
|
|
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
|
|
change_type: new_component
|
|
|
|
# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
|
|
component: cloudfoundry
|
|
|
|
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
|
|
note: Adds a resource convention for Cloud Foundry applications and system components.
|
|
|
|
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
|
|
# The values here must be integers.
|
|
issues: [622, 624]
|
|
|
|
# (Optional) One or more lines of additional information to render under the primary note.
|
|
# These lines will be padded with 2 spaces and then inserted directly into the document.
|
|
# Use pipe (|) for multiline entries.
|
|
subtext: |
|
|
Introduces a description for CloudFoundry resources. These can either be
|
|
applications deployed on the runtime or system components of Cloud Foundry
|
|
itself. It also extends to the runtime logs and metrics, e.g. Gorouter access
|
|
logs and container metrics.
|