Setting-up NPM registry for dgbuilder
This commit is showing-up how OOM patches must be handled in casablanca
release. In Dublin we would like to avoid this completely OOM-1610
so here we are just reproducing the same logic which was already
implemented in Beijing for bash offline installer.
In general it works in a way that OOM charts are patched during
offline platform build and values are configured in install time using
pre-install application role/hook.
Change-Id: I1a2425ef63edd6bc08dcecf0fcae7fd6e553d0ed
Issue-ID: OOM-1616
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
diff --git a/patches/onap-casablanca-patch-role/tasks/main.yml b/patches/onap-casablanca-patch-role/tasks/main.yml
new file mode 100644
index 0000000..a7064b1
--- /dev/null
+++ b/patches/onap-casablanca-patch-role/tasks/main.yml
@@ -0,0 +1,24 @@
+---
+# This role contains patching logic for OOM charts
+# and is valid until OOM-1610 is implemented
+- name: Patch OOM - nexus domain resolving
+ lineinfile:
+ path: "{{ app_helm_charts_infra_directory }}/{{ item }}"
+ regexp: '^(.*)HOSTS_FILE_RECORD'
+ line: '\g<1>{{ cluster_ip }} {{ simulated_hosts.nexus | join(" ") }} >> /etc/hosts;'
+ backrefs: yes
+ state: present
+ with_items:
+ - common/dgbuilder/templates/deployment.yaml
+ - sdnc/charts/sdnc-portal/templates/deployment.yaml
+
+- name: Patch OOM - set npm registry
+ lineinfile:
+ path: "{{ app_helm_charts_infra_directory }}/{{ item }}"
+ regexp: '^(.*)NPM_REGISTRY_RECORD'
+ line: '\g<1>npm set registry "http://nexus.{{ ansible_nodename }}/repository/npm-private/";'
+ backrefs: yes
+ state: present
+ with_items:
+ - common/dgbuilder/templates/deployment.yaml
+ - sdnc/charts/sdnc-portal/templates/deployment.yaml