Could you do a demo on a more practical use case? For this case, we can simply define our own variables, right? instead of injecting custom facts into managed nodes
1. Yes, we will have more real-life use cases in the series later. 2. Facts are somewhat different from variables. Facts are fixed items (like system details) which you can refer for your playbook decisions.
I agree with Gineesh. Facts are customized more than a system variable I would use custom facts to keep a record of the 1) Application being hosted on the server 2) Business module 3) Business criticality: Mission critical/Non mission critical 4) The type of environment and many other facts relating to the application hosted.
Ansible Full Course Playlist : ruclips.net/video/K4wGqwS2RLw/видео.html
very helpful. tnx
Thank you. Glad to hear that.
Could you do a demo on a more practical use case? For this case, we can simply define our own variables, right? instead of injecting custom facts into managed nodes
1. Yes, we will have more real-life use cases in the series later.
2. Facts are somewhat different from variables. Facts are fixed items (like system details) which you can refer for your playbook decisions.
Check Ansible Real Life Use case here
techbeatly.com/ansible-real-life
I agree with Gineesh.
Facts are customized more than a system variable I would use custom facts to keep a record of the
1) Application being hosted on the server
2) Business module
3) Business criticality: Mission critical/Non mission critical
4) The type of environment
and many other facts relating to the application hosted.
🤝
Sir it is not necessary to have execute permission on custom fact file right? :-) please reply
Custom fact file is a simple text file. no need execute permission. (as per my understanding)
@@techbeatly yes you are right use,I've searched about it thanks for the reply :)
😉🤝