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

Project Discussions
21

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, and don’t take them from the Galaxy artifacts.)

1 Like
22

@felixfontein here are the new repos:

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

23

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
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.
1 Like