[v1.26.x] unpin cryptography dependency for ansible-operator base images (#6290)

* unpin cryptography dependency for ansible-operator base images

Signed-off-by: Bryce Palmer <[email protected]>

* fix .cncf-maintainers sanity failure

Signed-off-by: Bryce Palmer <[email protected]>

* fix OWNERS_ALIASES

Signed-off-by: Bryce Palmer <[email protected]>

* update dead links

Signed-off-by: Bryce Palmer <[email protected]>

---------

Signed-off-by: Bryce Palmer <[email protected]>
Co-authored-by: Bryce Palmer <[email protected]>

Author: openshift-cherrypick-robot

OWNERS_ALIASES

@@ -5,9 +5,9 @@ aliases:
   # Contributors who can be contacted to perform admin-related tasks on the repo.
   # This role is a subset of the approver role.
   sdk-admins:
-  - asmacdo
-  - jmrodri
   - joelanford
+  - everettraven
+  - oceanc80
 
   # Contributors who can approve any PRs in the repo.
   sdk-approvers:
@@ -16,7 +16,8 @@ aliases:
   - rashmigottipati
   - theishshah
   - varshaprasad96
-  - everettraven
+  - grokspawn
+  - anik120
 
   # Contributors who can review and LGTM any PRs in the repo.
   sdk-reviewers:
@@ -30,3 +31,5 @@ aliases:
   - estroz
   - camilamacedo86
   - marc-obrien
+  - asmacdo
+  - jmrodri

images/ansible-operator-2.11-preview/Pipfile

@@ -9,10 +9,7 @@ ansible-runner-http = "==1.0.0"
 ipaddress = "==1.0.23"
 openshift = "~=0.13.0"
 jmespath = "==0.10.0"
-# cryptography needs to be pinned to 3.3.2 as this is the last version
-# before its setup requires rust, which is not available via RPM in the
-# base image. This pin should be re-evaluated once the base image is updated.
-cryptography = "==3.3.2"
+cryptography = "*"
 ansible-core = "~=2.11.0"
 oauthlib = "==3.2.1"
 

images/ansible-operator-2.11-preview/Pipfile.lock

@@ -10,10 +10,7 @@ ipaddress = "==1.0.23"
 openshift = "~=0.13.0"
 ansible = "~=2.9.15"
 jmespath = "==0.10.0"
-# cryptography needs to be pinned to 3.3.2 as this is the last version
-# before its setup requires rust, which is not available via RPM in the
-# base image. This pin should be re-evaluated once the base image is updated.
-cryptography = "==3.3.2"
+cryptography = "*"
 oauthlib = "==3.2.1"
 
 [dev-packages]

images/ansible-operator/Pipfile

@@ -48,7 +48,7 @@ Our molecule scenarios have the following basic structure:
 └── verify.yml
 ```
 
-- `molecule.yml` is a configuration file for molecule. It defines what driver to use to stand up an environment and the associated configuration, linting rules, and a variety of other configuration options. For full documentation on the options available here, see the [molecule configuration documentation](https://molecule.readthedocs.io/en/latest/configuration.html)
+- `molecule.yml` is a configuration file for molecule. It defines what driver to use to stand up an environment and the associated configuration, linting rules, and a variety of other configuration options. For full documentation on the options available here, see the [molecule configuration documentation](https://molecule.readthedocs.io/en/latest/configuration/)
 
 - `prepare.yml` is an Ansible playbook that is run once during the set up of a scenario. You can put any arbitrary Ansible in this playbook. It is used for one-time configuration of your test environment, for example, creating the cluster-wide `CustomResourceDefinition` that your Operator will watch.
 

images/ansible-operator/Pipfile.lock

@@ -1288,7 +1288,7 @@ which ./bin/openapi-gen > /dev/null || go build -o ./bin/openapi-gen k8s.io/kube
 The Molecule version for Ansible based-operators was upgraded from `2.22` to `3.0.2`. The following changes are required in the default scaffold files.
 
 - Remove the `scenario.name` from `molecule.yaml` and then, ensure that any condition with will look for the folder name which determines the scenario name from now on
-- Replace the lint with newer syntax from [documentation](https://molecule.readthedocs.io/en/latest/configuration.html#lint). See:
+- Replace the lint with newer syntax. See:
 
 Replace: