← Please visit roadmap.octopus.com Settings and activity 2 results found Add TaskId and/or DeploymentId to the Deployment Journal 1 vote Vote Vote Vote We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close Vote We’ll send you updates on this idea 0 comments · Product Feedback » Deployments · Edit… · Delete… · Admin → Kyle Shanafelt shared this idea · October 18, 2017 Provide ability to add metadata to machines and environments 4 votes Vote Vote Vote We're glad you're herePlease sign in to leave feedback Signed in as (Sign out) Close Close Vote We’ll send you updates on this idea 2 comments · Product Feedback » Installation · Delete… · Admin → An error occurred while saving the comment Kyle Shanafelt commented · April 29, 2016 · Edit… · Delete… Ideally metadata would also map the default data already present: We have Display name, style, thumbprint, and url which all lend themselves to key value pairs the Disable this target box could be either a tag (i.e. disabled) or a value pair (disabled: true) Environments, and Roles would make a usable, but possibly awkward key value pair: (i.e. Environments: [Dev, Prerelease, Release] Save Submitting... Kyle Shanafelt supported this idea · April 29, 2016
Ideally metadata would also map the default data already present:
We have Display name, style, thumbprint, and url which all lend themselves to key value pairs
the Disable this target box could be either a tag (i.e. disabled) or a value pair (disabled: true)
Environments, and Roles would make a usable, but possibly awkward key value pair: (i.e. Environments: [Dev, Prerelease, Release]