Skip to content

Conversation

@MuleDad
Copy link

@MuleDad MuleDad commented Dec 30, 2025

For a Blue Button Host Pool Deployment, when using a Custom Script/App to run during the deployment, the regex doesn't accept periods, so something like putty-0.83 would fail. I saw that there is a character limit of 13 that I was going to change, but I'm wondering if maybe that limit is there because you use the value to create a local folder to copy and run from and you wanted to stay under a 15 character limit. If there is no reason to have a limit, then I would like it bigger so that I can build my automation to use the file name from the artifacts container minus the extension.

@shawntmeyer
Copy link
Contributor

have you verified that run commands can have periods in their names? The blob name can definitely have periods so that part shouldn't be an issue

@MuleDad
Copy link
Author

MuleDad commented Jan 5, 2026

It's not the blob, it's the regex for the Name field, it use to work but looks like the period was removed from the syntax. It's not letting me attach a picture, but if you go to Session Hosts tabs, change Custom Scripts to Yes, and then type VSCode_1.107 in the Customization Name field, the helper text says 'The value must not contain spaces or end or begin with a dash or underscore. The value must not be empty.' That field is also now limited to 13 characters, I wasn't sure if that was due to a reuse of the name for creating the local folder or something, but if there is not a technical reason, more character would be nice, but not required.

@shawntmeyer
Copy link
Contributor

I fixed the issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants