# \[Default date 2025-04-03\] Collection inclusion: include microsoft.iis in the Ansible community package

**URL:** <https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017>\
**Category:** Project Discussions\
**Tags:** community-wg\
**Created:** [March 13, 2025, 10:14am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017 "2025-03-13T10:14:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [March 13, 2025, 10:14am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/1 "2025-03-13T10:14:27Z")

</div>

Discussion: [New collection microsoft.iis · ansible-collections/ansible-inclusion · Discussion #78 · GitHub](https://github.com/ansible-collections/ansible-inclusion/discussions/78)

I’ve conducted a first review, and the collection imo satisfies the requirements and ready for inclusion.

Could anybody from the [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) conduct the second short review as specified in the [comment](https://github.com/ansible-collections/ansible-inclusion/discussions/78#discussioncomment-12448495)? i.e. to check **only** the following would be enough (just copy this to a comment in the discussion and go through it):

- follows the [Ansible documentation standards](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html) and the [style guide](https://docs.ansible.com/ansible/devel/dev_guide/style_guide/index.html#style-guide)
- follows [development conventions](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html); as well as these other requirements:
  - modules satisfy the concept of [idempotency](https://docs.ansible.com/ansible/latest/reference_appendices/glossary.html#term-Idempotency%3E)
  - modules that only gather information are named `<something>_info`
  - modules that return `ansible_facts` are named `<something>_facts` and do not return non-facts
  - other modules must not allow querying information using specific `state` option values, or similar mechanisms (like `state=get` or `state=query`). These features should be moved to `<something>_info` or `<something>_fact` modules.
  - `check_mode` is supported in all `_info` and `_facts` modules

Thanks

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [March 18, 2025, 8:50am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/2 "2025-03-18T08:50:10Z")

</div>

[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) could anybody please review? Otherwise, we should change the policy to make one review sufficient for inclusion if there are no volunteers within SC for a week or so.  
The list of the items to check is very short, shouldn’t take longer than 15 minutes max to check a few modules.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [March 23, 2025, 10:01am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/3 "2025-03-23T10:01:51Z")

</div>

It’s kind of hard to review a PowerShell collection if you don’t know PowerShell. I’m not sure how many folks in SC know enough about PowerShell to be able to do a good review for this one, but I guess the number is smaller than the number of all persons in the SC. (Well it definitely is, since I’m at least one such person…)

Anyway, I don’t think reducing requirements is a solution to the review problem.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [March 24, 2025, 6:30am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/4 "2025-03-24T06:30:34Z")

</div>

@felixfontein thanks for reviewing the collection!

1. Jordan fixed the stuff you found, PTAL
2. Another option could be a rotation of sort. I’m gonna raise a dedicated topic as soon as we solve this and the [other request](https://forum.ansible.com/t/needs-second-review-collection-inclusion-include-hitachis-vsp-one-storage-in-the-ansible-community-package/41262).

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [March 27, 2025, 12:07pm UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/5 "2025-03-27T12:07:42Z")

</div>

The collection got the second approval (thanks @gundalow).  
The default inclusion date is `2025-04-03`. FYI

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [March 27, 2025, 12:49pm UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/6 "2025-03-27T12:49:57Z")

</div>

> [@felixfontein](#):
>
> It’s kind of hard to review a PowerShell collection if you don’t know PowerShell.

I’ve done the 2nd review. While I don’t know Powershell, I know that Jordan’s previous collections are to a high standard. So I felt comfortable approving this.

I don’t think we need to reduce the requirements either.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [April 3, 2025, 5:42am UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/7 "2025-04-03T05:42:30Z")

</div>

As no objections were raised, let’s proceed with inclusion by adding it to ansible-builtin-data

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [April 3, 2025, 2:54pm UTC](https://forum.ansible.com/t/default-date-2025-04-03-collection-inclusion-include-microsoft-iis-in-the-ansible-community-package/41017/8 "2025-04-03T14:54:34Z")

</div>

[Add microsoft.iis to Ansible 11+](https://github.com/ansible-community/ansible-build-data/pull/525)
