-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with global_properties when properties contain a dash "-" #729
Comments
it's something we also faced recently while working on an internal project, can't find now a specific reference but you can try a workaround defining those as: audit:
alfresco-access.enabled: false
alfresco-access.sub-actions.enabled: false |
@gionn : Maybe I'm missing something but when I tried with your suggestion, I had the exact same behavior as before. Definition of the global_properties:
...
aos:
baseUrlOverwrite: >-
{{ acs_play_proto }}://{{ fqdn_alfresco | default(nginx_host) }}:{{ acs_play_port }}/alfresco/aos
audit:
enabled: "false"
cmischangelog:
enabled: "false"
sync:
enabled: "false"
tagging:
enabled: "false"
alfresco-access.enabled: "false"
alfresco-access.sub-actions.enabled: "false"
heartbeat:
enabled: "false" That generated the following content on the newly installed server: aos.baseUrlOverwrite=https://mydns.com:443/alfresco/aos
audit.enabled=false
audit.cmischangelog.enabled=false
audit.sync.enabled=false
audit.tagging.enabled=false
audit['alfresco-access.enabled']=false
audit['alfresco-access.sub-actions.enabled']=false
heartbeat.enabled=false Therefore, whether I use global_properties:
audit:
alfresco-access:
enabled: "false"
sub-actions:
enabled: "false" or global_properties:
audit:
alfresco-access.enabled: "false"
alfresco-access.sub-actions.enabled: "false" I have the same outcome. Well it is not 100% the same file I will do 1 more try with the following to see if the behavior changes: global_properties:
audit.alfresco-access.enabled: "false"
audit.alfresco-access.sub-actions.enabled: "false" |
So I can confirm that the workaround requires the 1st word of the line to not contain any "-". Therefore, the following works properly: global_properties:
audit:
enabled: "false"
cmischangelog:
enabled: "false"
sync:
enabled: "false"
tagging:
enabled: "false"
audit.alfresco-access.enabled: "false"
audit.alfresco-access.sub-actions.enabled: "false"
heartbeat:
enabled: "false" Generated the correct content in the audit.enabled=false
audit.cmischangelog.enabled=false
audit.sync.enabled=false
audit.tagging.enabled=false
audit.alfresco-access.enabled=false
audit.alfresco-access.sub-actions.enabled=false
heartbeat.enabled=false |
Thanks for taking time to sort it out. The bug actually is within the usage of ansible.utils.to_paths to convert the complex object of alfresco-ansible-deployment/roles/repository/templates/alfresco-global.properties.j2 Line 1 in 18b51f9
could be a bug in ansible as well, but we never had time to investigate further. |
Bug description
I was playing/testing the
global_properties
definition but while doing so, it appears that Alfresco properties that are set like that fails to be setup properly in thealfresco-global.properties
file when said property contains a dash (-
).Here is the example of
global_properties
that I tried:And the generated
alfresco-global.properties
:As you can see above, all properties appears to be set properly except for the 2 lines with
alfresco-access
orsub-actions
.Ansible error
No errors at Ansible level:
The text was updated successfully, but these errors were encountered: