# ACP: What to do with purestorage.flashblade and flasharray?

**URL:** <https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435>\
**Category:** Project Discussions\
**Tags:** community-wg\
**Created:** [October 7, 2026, 3:25pm UTC](https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435 "2026-10-07T15:25:26Z")\
**Posts on this page:** 3\
**Page:** 2

<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:** [October 26, 2026, 7:28pm UTC](https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435/21 "2026-10-26T19:28:31Z")

</div>

From our side you don’t need to publish new versions on Galaxy, simply having a repository + a tag for that repository that produces the source for the latest purestorage.\* versions on Galaxy would be good enough for us. (We track the repository names in [ansible-build-data/15/collection-meta.yaml at main · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/blob/main/15/collection-meta.yaml#L305-L308), and don’t take them from the Galaxy artifacts.)

---

<div class="post-metadata">

**Author:** ![sdodsley](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sdodsley/32/655_2.png) [@sdodsley](https://forum.ansible.com/u/sdodsley)\
**Post date:** [October 26, 2026, 7:31pm UTC](https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435/22 "2026-10-26T19:31:39Z")

</div>

@felixfontein here are the new repos:

> **[GitHub - Everpure-Ansible/purestorage.flasharray: Deprecated redirect-only shim for...](https://github.com/Everpure-Ansible/purestorage.flasharray)**
>
> Deprecated redirect-only shim for purestorage.flasharray, renamed to everpure.flasharray

> **[GitHub - Everpure-Ansible/purestorage.flashblade: Deprecated redirect-only shim for...](https://github.com/Everpure-Ansible/purestorage.flashblade)**
>
> Deprecated redirect-only shim for purestorage.flashblade, renamed to everpure.flashblade

Let me know if there is anything else you need me to do.

---

<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:** [October 26, 2026, 8:11pm UTC](https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435/23 "2026-10-26T20:11:36Z")

</div>

I created a PR to update the Ansible build data: [purestorage.flash(array|blade) has been renamed to everpure.flash(array|blade) by felixfontein · Pull Request #745 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/pull/745)  
Once that’s merged:

1. The next Ansible 14 release will contain the new everpure.\* collections next to the older versions of purestorage.\*; the Ansible 14 documentation will announce that purestorage.\* are deprecated and have been renamed;
2. The next Ansible 15 pre-release will contain the redirecting versions of purestorage.\* next to the everpure.\* collections;
3. In Ansible 17 the purestorage.\* collections (which contain only redirects) will be removed.

[Previous page](https://forum.ansible.com/t/acp-what-to-do-with-purestorage-flashblade-and-flasharray/46435.md?page=1)