WebSites: Binding infos not supported
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- devops, infrastructure
Research direction
Start with the WebSites composite resource and the DSC configuration shown in the issue, then trace how BindingInfo is represented during MOF compilation. Reproduce the failure with the HTTPS binding example; done means the configuration compiles without the STRING[] to INSTANCE[] conversion error and supports the supplied binding properties.
Written by the indexing model from the issue text.
Description
Problem description
Specifying the binding infos for a website, the MOF compilation fails.
Verbose logs
Write-NodeMOFFile : Invalid MOF definition for node 'localhost_WebSites': Exception calling "ValidateInstanceText" with "1" argument(s): "Convert property 'BindingInfo' value from type
'STRING[]' to type 'INSTANCE[]' failed
DSC configuration
Items:
- Name: TestSite1
ApplicationPool: TestAppPool1
BindingInfo:
Protocol: HTTPS
Port: 443
HostName: test.com
CertificateThumbprint: 466CD26A6E2F346A3A813D12E2BAAD0E886E7BBF
- Name: TestSite2
ApplicationPool: TestAppPool2
# Remove IIS Default WebSite
- Name: Default Web Site
Ensure: Absent
Operating system the target node is running
OsName : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : en-US
OsMuiLanguages : {en-US}
PowerShell version and build the target node is running
Name Value
---- -----
PSVersion 5.1.19041.1320
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.1320
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
CommonTasks version
0.4
- Dominant language
- PowerShell
- Stars
- 45
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dsccommunity/CommonTasks
-
bug
dsccommunity/CommonTasks#250 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dsccommunity/CommonTasks#238 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
dsccommunity/CommonTasks#228 ·
-
Add Codeowners file Open
Difficulty 1/5 Under an hour Newbie friendliness 30/100
dsccommunity/CommonTasks#227 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
dsccommunity/CommonTasks#226 ·
All issues in dsccommunity/CommonTasks
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·