Skip to content

Commit 01f95e2

Browse files
authored
xExchange: Update repository to use the latest pipeline (#471)
- xExchange - Update repository to use the latest pipeline (issue #466).
1 parent 9198ec7 commit 01f95e2

24 files changed

+980
-435
lines changed

.gitattributes

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Needed for publishing of examples, build worker defaults to core.autocrlf=input.
2-
* text eol=crlf
2+
* text eol=autocrlf
3+
4+
*.mof text eol=crlf
5+
*.sh text eol=lf
6+
*.svg eol=lf
37

48
# Ensure any exe files are treated as binary
59
*.exe binary
@@ -10,3 +14,7 @@
1014

1115
# Allow test .PFX files to be saved as binary files
1216
*.pfx binary
17+
18+
*.png binary
19+
*.dll binary
20+
*.so binary

.github/ISSUE_TEMPLATE/Problem_with_resource.md

Lines changed: 0 additions & 63 deletions
This file was deleted.
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
name: Problem with a resource
2+
description: If you have a problem, bug, or enhancement with a resource in this resource module.
3+
labels: []
4+
assignees: []
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Please prefix the issue title (above) with the resource name, e.g. 'ResourceName: Short description of my issue'!
10+
11+
Your feedback and support is greatly appreciated, thanks for contributing!
12+
- type: textarea
13+
id: description
14+
attributes:
15+
label: Problem description
16+
description: Details of the scenario you tried and the problem that is occurring.
17+
validations:
18+
required: true
19+
- type: textarea
20+
id: logs
21+
attributes:
22+
label: Verbose logs
23+
description: |
24+
Verbose logs showing the problem. **NOTE! Sensitive information should be obfuscated.** _Will be automatically formatted as plain text._
25+
placeholder: |
26+
Paste verbose logs here
27+
render: text
28+
validations:
29+
required: true
30+
- type: textarea
31+
id: configuration
32+
attributes:
33+
label: DSC configuration
34+
description: |
35+
The DSC configuration that is used to reproduce the issue (as detailed as possible). **NOTE! Sensitive information should be obfuscated.** _Will be automatically formatted as PowerShell code._
36+
placeholder: |
37+
Paste DSC configuration here
38+
render: powershell
39+
validations:
40+
required: true
41+
- type: textarea
42+
id: suggestedSolution
43+
attributes:
44+
label: Suggested solution
45+
description: Do you have any suggestions how to solve the issue?
46+
validations:
47+
required: true
48+
- type: textarea
49+
id: targetNodeOS
50+
attributes:
51+
label: Operating system the target node is running
52+
description: |
53+
Please provide as much as possible about the target node, for example edition, version, build, and language. _Will be automatically formatted as plain text._
54+
55+
On OS with WMF 5.1 the following command can help get this information: `Get-ComputerInfo -Property @('OsName','OsOperatingSystemSKU','OSArchitecture','WindowsVersion','WindowsBuildLabEx','OsLanguage','OsMuiLanguages')`
56+
placeholder: |
57+
Add operating system information here
58+
render: text
59+
validations:
60+
required: true
61+
- type: textarea
62+
id: exchangeVersion
63+
attributes:
64+
label: Exchange Server edition and version the target node is running
65+
description: |
66+
Please provide as much as possible about the Exchange Server that runs on the target node, for example edition, version, build, and language. _Will be automatically formatted as plain text._
67+
68+
The following command can help get this information: `Get-ExchangeServer | ft ServerRole, Edition, AdminDisplayVersion`
69+
placeholder: |
70+
Add Exchange Server information here
71+
render: text
72+
validations:
73+
required: true
74+
- type: textarea
75+
id: targetNodePS
76+
attributes:
77+
label: PowerShell version and build the target node is running
78+
description: |
79+
Please provide the version and build of PowerShell the target node is running. _Will be automatically formatted as plain text._
80+
81+
To help with this information, please run this command: `$PSVersionTable`
82+
placeholder: |
83+
Add PowerShell information here
84+
render: text
85+
validations:
86+
required: true
87+
- type: textarea
88+
id: moduleVersion
89+
attributes:
90+
label: xExchange version
91+
description: |
92+
Please provide the version of the xExchange module that was used. _Will be automatically formatted as plain text._
93+
94+
To help with this information, please run this command: `Get-Module -Name 'xExchange' -ListAvailable | ft Name,Version,Path`
95+
placeholder: |
96+
Add module information here
97+
render: text
98+
validations:
99+
required: true

.github/ISSUE_TEMPLATE/Resource_proposal.md

Lines changed: 0 additions & 21 deletions
This file was deleted.
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
name: New resource proposal
2+
description: If you have a new resource proposal that you think should be added to this resource module.
3+
title: "NewResourceName: New resource proposal"
4+
labels: []
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Please replace `NewResourceName` in the issue title (above) with your proposed resource name.
11+
12+
Thank you for contributing and making this resource module better!
13+
- type: textarea
14+
id: description
15+
attributes:
16+
label: Resource proposal
17+
description: Provide information how this resource will/should work and how it will help users.
18+
validations:
19+
required: true
20+
- type: textarea
21+
id: proposedProperties
22+
attributes:
23+
label: Proposed properties
24+
description: |
25+
List all the proposed properties that the resource should have (key, required, write, and/or read). For each property provide a detailed description, the data type, if a default value should be used, and if the property is limited to a set of values.
26+
value: |
27+
Property | Type qualifier | Data type | Description | Default value | Allowed values
28+
--- | --- | --- | --- | --- | ---
29+
PropertyName | Key | String | Detailed description | None | None
30+
validations:
31+
required: true
32+
- type: textarea
33+
id: considerations
34+
attributes:
35+
label: Special considerations or limitations
36+
description: |
37+
Provide any considerations or limitations you can think of that a contributor should take in account when coding the proposed resource, and or what limitations a user will encounter or should consider when using the proposed resource.
38+
validations:
39+
required: true

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: "Virtual PowerShell User Group #DSC channel"
4+
url: https://dsccommunity.org/community/contact/
5+
about: "To talk to the community and maintainers of DSC Community, please visit the #DSC channel."
6+

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@
1111
You may remove this comment block, and the other comment blocks, but please
1212
keep the headers and the task list.
1313
-->
14+
1415
#### Pull Request (PR) description
16+
1517
<!--
1618
Replace this comment block with a description of your PR.
1719
Also, make sure you have updated the CHANGELOG.md, see the
@@ -20,15 +22,18 @@
2022
-->
2123

2224
#### This Pull Request (PR) fixes the following issues
25+
2326
<!--
2427
If this PR does not fix an open issue, replace this comment block with None.
2528
If this PR resolves one or more open issues, replace this comment block with
26-
a list the issues using a GitHub closing keyword, e.g.:
27-
- Fixes #123
28-
- Fixes #124
29+
a list of the issues using a GitHub closing keyword, e.g.:
30+
31+
- Fixes #123
32+
- Fixes #124
2933
-->
3034

3135
#### Task list
36+
3237
<!--
3338
To aid community reviewers in reviewing and merging your PR, please take
3439
the time to run through the below checklist and make sure your PR has
@@ -37,6 +42,7 @@
3742
Change to [x] for each task in the task list that applies to your PR.
3843
For those task that don't apply to you PR, leave those as is.
3944
-->
45+
4046
- [ ] Added an entry to the change log under the Unreleased section of the
4147
file CHANGELOG.md. Entry should say what was changed and how that
4248
affects users (if applicable), and reference the issue being resolved

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
1+
.vs
2+
.vscode
13
output/

.vscode/settings.json

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,15 @@
77
"powershell.codeFormatting.whitespaceAroundOperator": true,
88
"powershell.codeFormatting.whitespaceAfterSeparator": true,
99
"powershell.codeFormatting.ignoreOneLineBlock": false,
10-
"powershell.codeFormatting.pipelineIndentationStyle": "IncreaseIndentationAfterEveryPipeline",
10+
"powershell.codeFormatting.pipelineIndentationStyle": "IncreaseIndentationForFirstPipeline",
1111
"powershell.codeFormatting.preset": "Custom",
1212
"powershell.codeFormatting.alignPropertyValuePairs": true,
13-
"files.trimTrailingWhitespace": true,
14-
"files.insertFinalNewline": true,
13+
"powershell.developer.bundledModulesPath": "${cwd}/output/RequiredModules",
1514
"powershell.scriptAnalysis.settingsPath": ".vscode\\analyzersettings.psd1",
1615
"powershell.scriptAnalysis.enable": true,
16+
"files.trimTrailingWhitespace": true,
17+
"files.trimFinalNewlines": true,
18+
"files.insertFinalNewline": true,
1719
"files.associations": {
1820
"*.ps1xml": "xml"
1921
},

.vscode/tasks.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
"label": "build",
4242
"type": "shell",
4343
"command": "&${cwd}/build.ps1",
44-
"args": ["-AutoRestore"],
44+
"args": [],
4545
"presentation": {
4646
"echo": true,
4747
"reveal": "always",

0 commit comments

Comments
 (0)