:question: When deploying metaflow with the minima...
# ask-metaflowa
adventurous-plastic-90730
05/17/2023, 7:16 PM❓ When deploying metaflow with the minimal aws example, we ran into a situation where the terraform plan worked but the terraform apply via CI failed because there were unexpected tags. I reported the issue but I'm curious if anyone else has run into this and what, if anything, I can do to make the prod deploy via CI smoother than the dev deploy.
✅ 1
👀 1
a
average-beach-28850
05/17/2023, 9:13 PMthat links goes to a private google doc but I think you meant this
average-beach-28850
05/17/2023, 9:14 PMi haven't run into this, do you use any custom tags there? there are some threads on terraform github where this happens where people try to use current timestamp in tags and some other dynamic things like that
a
adventurous-plastic-90730
05/18/2023, 3:58 PMwe had an alternative hypothesis the issues had something to do with the interaction between our stack and this module. it sounds like that might be the case.
adventurous-plastic-90730
05/19/2023, 6:55 PMCould it be this part of the suggested minimal example metaflow.tf that is causing tag conflicts on apply?
Copy code
tags = {
"managedBy" = "terraform"
}b
bright-author-73055
08/18/2023, 2:57 PMBumping this thread! @adventurous-plastic-90730 were you able to get past this? We're currently running into this on our team
bright-author-73055
08/18/2023, 5:26 PMNot exactly sure what it was, but re-ran everything with the tag changed to:
Copy code
tags = {
"managedBy" = "metaflow-terraform"
}a
adventurous-plastic-90730
08/21/2023, 2:02 PM@bright-author-73055 we ended up forking the repo because we had other reasons to do so and managed this and some auth terraform that way.
b
bright-author-73055
08/21/2023, 2:28 PM@adventurous-plastic-90730 gotcha gotcha makes sense. Thanks!! 🙂
👍 1
4 Views