OctopusDeploy
Structured Configuration Replacement trims colons within YAML files
Severity
1 customer affected
Version
2023.4.8116, 2024.1.2962
Latest Version
None
What happened?
When running structured configuration replacement against a YAML file some colons are being trimmed at the end of headings, even if no replacements are being done within the file.
It seems like the spacing is changing on the deployed YAML as well, see screenshots for line number changes.
Reproduction
- Setup a process to deploy a package that has a YAML file within it. Make sure the YAML has at least one heading with a colon (e.g.
setup.test:) - Set "Structure Configuration Replacement" feature on the step and include
*.yml(note: no actual variables to replace are necessary) - Run the deployment
- Observer inside deployed YAML that the colon from the heading is missing
Error and Stacktrace
No response
More Information
Screenshot examples from testing with a customers YAML
Deployment without replacement check:
Deployment with replacement check:
Workaround
Explicitly state the null value, rather than leaving it empty.
The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.
