You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified the problem exists in the latest version
I have searched open and closed issues to make sure it isn't already reported
I have written a descriptive issue title
I have linked the original source of this report
I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
The bug
When an integer is entered as a label value it ends up in the yaml as an integer and gets interrupted as such down the line. This has lead to problems where strings are expected.
What I expected to happen
The values should be quoted, as the Annotations are.
Affected versions
Octopus Server:
Workarounds
None
Links
Raised internally.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Feb 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
The bug
When an integer is entered as a label value it ends up in the yaml as an integer and gets interrupted as such down the line. This has lead to problems where strings are expected.
What I expected to happen
The values should be quoted, as the Annotations are.
Affected versions
Octopus Server:
Workarounds
None
Links
Raised internally.
The text was updated successfully, but these errors were encountered: