IBX-3767: Document how to use fastly CLI on post deploy hook (#57)

* IBX-3767: Document how to use fastly CLI on post deploy hook

* fix: Add custom snippet

resources/platformsh/ibexa-content/4.3.x-dev/.platform.app.yaml

@@ -210,6 +210,12 @@ hooks:
         # Depending on your VCL, buy default this would trigger a soft purge (expiry) and allow grace period, however
         # even so if your change only affected certain subset of content, ideally you should only clear specific tags:
         ##bin/console fos:httpcache:invalidate:tag l44 c33 ct2 ...
+        
+        # It is possible to manipulate your Fastly VCL configuration directly from command line using Fastly CLI. 
+        # Official documentation on how to install: https://developer.fastly.com/learning/tools/cli#installing 
+        # Example VCL snippet upload using vcl_recv hook (remember about FASTLY_SERVICE_ID and FASTLY_KEY environmental variables):
+        ##fastly vcl custom create --name="Ibexa VCL" --main --version=latest --autoclone  --content=vendor/ibexa/fastly/fastly/ez_main.vcl
+        ##fastly vcl snippet create --name="Shielding" --version=active --autoclone --type recv --content=vendor/ibexa/fastly/fastly/snippet_re_enable_shielding.vcl
 
     # Post deploy hook, like deploy but after being deployed and live, for deploy tasks we can do asynchronously
     # Tip: As this is running while web is running, and it's async, avoid doing anything like cache clearing that affects web requests here.

resources/platformsh/ibexa-content/4.3/.platform.app.yaml

@@ -210,6 +210,12 @@ hooks:
         # Depending on your VCL, buy default this would trigger a soft purge (expiry) and allow grace period, however
         # even so if your change only affected certain subset of content, ideally you should only clear specific tags:
         ##bin/console fos:httpcache:invalidate:tag l44 c33 ct2 ...
+        
+        # It is possible to manipulate your Fastly VCL configuration directly from command line using Fastly CLI. 
+        # Official documentation on how to install: https://developer.fastly.com/learning/tools/cli#installing 
+        # Example VCL snippet upload using vcl_recv hook (remember about FASTLY_SERVICE_ID and FASTLY_KEY environmental variables):
+        ##fastly vcl custom create --name="Ibexa VCL" --main --version=latest --autoclone  --content=vendor/ibexa/fastly/fastly/ez_main.vcl
+        ##fastly vcl snippet create --name="Shielding" --version=active --autoclone --type recv --content=vendor/ibexa/fastly/fastly/snippet_re_enable_shielding.vcl
 
     # Post deploy hook, like deploy but after being deployed and live, for deploy tasks we can do asynchronously
     # Tip: As this is running while web is running, and it's async, avoid doing anything like cache clearing that affects web requests here.

resources/platformsh/ibexa-experience/4.3.x-dev/.platform.app.yaml

@@ -210,6 +210,12 @@ hooks:
         # Depending on your VCL, buy default this would trigger a soft purge (expiry) and allow grace period, however
         # even so if your change only affected certain subset of content, ideally you should only clear specific tags:
         ##bin/console fos:httpcache:invalidate:tag l44 c33 ct2 ...
+        
+        # It is possible to manipulate your Fastly VCL configuration directly from command line using Fastly CLI. 
+        # Official documentation on how to install: https://developer.fastly.com/learning/tools/cli#installing 
+        # Example VCL snippet upload using vcl_recv hook (remember about FASTLY_SERVICE_ID and FASTLY_KEY environmental variables):
+        ##fastly vcl custom create --name="Ibexa VCL" --main --version=latest --autoclone  --content=vendor/ibexa/fastly/fastly/ez_main.vcl
+        ##fastly vcl snippet create --name="Shielding" --version=active --autoclone --type recv --content=vendor/ibexa/fastly/fastly/snippet_re_enable_shielding.vcl
 
     # Post deploy hook, like deploy but after being deployed and live, for deploy tasks we can do asynchronously
     # Tip: As this is running while web is running, and it's async, avoid doing anything like cache clearing that affects web requests here.