One change , we cannot use any name for the dynamic block, we need to name according to the resource type. For example if you use any other name other than ingress, it will throw an error.
Thank you!! one Q, @ 2:57 dynamic block name can be anything ? When I use an invalid block name like "ingress1" etc it says 'Blocks of type "ingress1" are not expected here.'. Works with only "ingress".
bro apne awesome series banaya h bs ek request h plz make some projects using terraform on aws where u will use things like elb autoscaling api gateways some realtime sceanario it could help us alot
Hello dear I really appreciate your inputs but I have full time job and family to take care of. So getting the time out of those are bit challenging and i am sharing everything here without any perks. It takes a lot of effort to prepare one session so that everyone like it. But definitely you will see it more
@@RahulWagh definitely bro u have ur work n woh hota h na jisse kuch sikhne ko mile toh hope badhne lagta h k kuch r sikhle n u r my senior, u can better guide me
great video. I just wanted to comment that in one section of the video you said dynamic block can have any name for example ingress that name will be used in the code. so if you had dynamic rahul then that block would be in the code
Hi Rahul thanks for this nice video. Dynamic block provides functionality to cater looping for attributes which are defined within resource object as we can use for_each and count for resources directly but not for blocks inside resources. Otherwise if it had been resource just to_set(port) and each.value could have been done but this will not be applicable to ingress/egress block within SG. Correct me if I am wrong . 🙏
Well the example which I have taken in the demo is just very basic you can definitely use for_each as well as count as per your need inside the terraform file
Thanks a lot for this concise, no BS tutorial!
Perfect. this is the task i got now and you made my life easy. thank you very much Rahul
Cheers
Awesome series, with clarity and concise on the topic!
Glad you like them!
Thank you sir because of I have started terraform tq fr teaching us.. May God provide a health and wealth God bless you
Thanks and keep enjoying
Very clearly explained, awesome
Glad you liked it
Rahul.. you are master man.
Glad you liked it
Great session sir
Very well explained!
One change , we cannot use any name for the dynamic block, we need to name according to the resource type. For example if you use any other name other than ingress, it will throw an error.
Thank you!! one Q, @ 2:57 dynamic block name can be anything ? When I use an invalid block name like "ingress1" etc it says 'Blocks of type "ingress1" are not expected here.'. Works with only "ingress".
You are right, we cannot name other than the actual resource type sub variables.
Thank you sir we really appreciate your effort.
How can we use credentials which is fetch from role in provider block?
bro apne awesome series banaya h bs ek request h plz make some projects using terraform on aws where u will use things like elb autoscaling api gateways some realtime sceanario it could help us alot
Thanks for liking- there are more in pipeline for terraform like vault, aws stuff
@@RahulWagh so make it bro why r u waiting for a channel like this helping us a lot
Hello dear I really appreciate your inputs but I have full time job and family to take care of. So getting the time out of those are bit challenging and i am sharing everything here without any perks.
It takes a lot of effort to prepare one session so that everyone like it.
But definitely you will see it more
@@RahulWagh definitely bro u have ur work n woh hota h na jisse kuch sikhne ko mile toh hope badhne lagta h k kuch r sikhle n u r my senior, u can better guide me
thank you !!!
You're welcome!
Very good sir
great video. I just wanted to comment that in one section of the video you said dynamic block can have any name for example ingress that name will be used in the code. so if you had dynamic rahul then that block would be in the code
really useful. thank you
Glad it was helpful!
Hi Rahul thanks for this nice video. Dynamic block provides functionality to cater looping for attributes which are defined within resource object as we can use for_each and count for resources directly but not for blocks inside resources. Otherwise if it had been resource just to_set(port) and each.value could have been done but this will not be applicable to ingress/egress block within SG. Correct me if I am wrong . 🙏
Well the example which I have taken in the demo is just very basic you can definitely use for_each as well as count as per your need inside the terraform file
could you please upload share the .txt file of this lab
Check Terraform official documentation
Ty....sir
You welcome
Hi Rahul