You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So having a template file, I would then from the deployment project modify those variable on the file adding if the ad present these vars. Then the formula here (hana) would just take the template file with the modified vars.
I have considered the pillar or other approaches/grains but I still considered that if we expose such files as template, it will be much more clear and easy to understand the whole machinery.
As alternative there is the grain approach where during the deployment, we set grains like ad_sapys_gid , ad_userid so and the formula here would take in case the exists.
On longerm, I think perhaps having a template file would simplify the install.
I was also thinking that the install function is to much "intelligent" or take to much responsability.
Imho we should split this call, in different phase:
create conf file
validate etc if needed
install
do post install if needed
Actually right now the install function is doing everything of this, which make difficult imho to have a fine grained debugging experience.
I will meanwhile explore the grain approach
The text was updated successfully, but these errors were encountered:
So I was researching how to inject the
gid
andid
for active directory integration and I found out that the best and elegant approach is to injecttemplate
files like https://github.com/SUSE/sapnwbootstrap-formula/blob/82f104952d812f4413920b8e38e63a95fc8984c5/netweaver/install_ascs.sls#L16So having a template file, I would then from the
deployment
project modify those variable on the file adding if thead
present these vars. Then the formula here (hana) would just take the template file with the modified vars.I have considered the
pillar
or other approaches/grains but I still considered that if we expose such files as template, it will be much more clear and easy to understand the whole machinery.As alternative there is the grain approach where during the deployment, we set grains like
ad_sapys_gid
,ad_userid
so and the formula here would take in case the exists.On longerm, I think perhaps having a template file would simplify the install.
I was also thinking that the
install
function is to much "intelligent" or take to much responsability.Imho we should split this call, in different phase:
Actually right now the install function is doing everything of this, which make difficult imho to have a fine grained debugging experience.
I will meanwhile explore the grain approach
The text was updated successfully, but these errors were encountered: