Комментарии:
This is great tutorial, i was wondering if I can setup similar workflow that uses env variable = dev and prod in terraform code to run on a particular deployment branch Dev or Main (prod) in GitHub based of the env variables in TF code as an example
variable "vmname" {
default = {
dev = "devcorpvm"
prod = "prodcorpvm"
}
Sir, i have a question regards this thing ..if any job failed to run then dependent job stops there. But what if jobs are ok (working fine) but deployment in env generates some error then how to handle that thing ? I have tried, but while deployment gets error still jobs are passed how to handle that case ? Thanks in advance..
ОтветитьGood one. Plese keep doing more on this
ОтветитьI got one question. In a real world project what conditions needs to be met in order to move from DEV to QA and then PROD, unit testing?
ОтветитьExcellent tutorial! Thank you for this.
Ответитьso where are the environments? where have you used those envs that you created? how to use it?
that MY_SECRET you'd created.
finally i got the solution thanks lot
ОтветитьThank you, exactly what I needed. Do you recommend having multiple branches to reflect this? Or just go off a main. What is best branching strategy for an actual production app
ОтветитьGreat video, thanks :)
Ответитьhow you explained this was so easy to understand it!!!! thanks!
ОтветитьEarned yourself a sub. Thanks for the content.
ОтветитьPerfectly explained :)
ОтветитьGood stuff. For completeness, it would have been nice to illustrate how to access environment secrets from steps.
ОтветитьLove it! Hope you could share more on GitHub actions.
ОтветитьThis is gold
ОтветитьThanks man
ОтветитьThis is exactly what I needed and a total pain without your vid. Thanks man, subbed!
ОтветитьThanks a lot Mickey, this is what something I was searching for
ОтветитьThis is awesome! Very much needed, and excellent implementation. :)
ОтветитьThanks! I learned something new!
Ответить