ansible-playbook: refactoring to better handle new docker registries

Bug #1940150 reported by Steven Webster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
Low
Unassigned

Bug Description

Brief Description
-----------------
The ansible-playbooks code should be re-factored to better handle the list of supported docker registries. This would make it easier and less error-prone to add new registries to the list.

An example of this is here:

https://review.opendev.org/c/starlingx/ansible-playbooks/+/803499

In which support for the github docker registry is added.

As can be seen, there are multiple tasks which reference the list of registries and their respective urls.

It would be nice if this could be defined once at a higher level.

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
Reference the above opendev review to see an example of the files that need to change when adding a new registry.

Expected Behavior
------------------
It would be nice to have a less error-prone method of adding a new registry.

Actual Behavior
----------------
Reference the above opendev review to see an example of the files that need to change when adding a new registry.

Tags: stx.config
Ghada Khalil (gkhalil)
tags: added: stx.config
Revision history for this message
Ghada Khalil (gkhalil) wrote :

screening: code improvement. No functional impact on stx operations

Changed in starlingx:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.