Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
I'm not sure I understood what you meant by: "but using atomic deployment and not as individual deployment commands"? Do you mean whether you can deploy only the other resources and not the state S3 bucket?
I was wondering if the S3 bucket has to be set up up front before the deployment can be performed? Just was wondering to see if even that can be automated like say one configuration that includes backend S3 creation and proceeding with the deployment only after backend is done.
But I played with it using your article and realised that backend has to be set up first. Also realised that the backend configuration does not accept variables and has to be constants that exist
Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
Yeah, exactly. Maybe in future they'll fix this DX issue of getting setup. But as you say the backend MUST be hardcoded (without some hacking) and therefore it must be created as a two step process where the first step is running on local (or some other backend other than the one you're configuring). It's a shame really... I imagine at some point this will get addressed. Glad you were able to follow through the tutorial though! At least the explanation wasn't terrible ! 😂
I'm not sure I understood what you meant by: "but using atomic deployment and not as individual deployment commands"? Do you mean whether you can deploy only the other resources and not the state S3 bucket?
I was wondering if the S3 bucket has to be set up up front before the deployment can be performed? Just was wondering to see if even that can be automated like say one configuration that includes backend S3 creation and proceeding with the deployment only after backend is done.
But I played with it using your article and realised that backend has to be set up first. Also realised that the backend configuration does not accept variables and has to be constants that exist
Yeah, exactly. Maybe in future they'll fix this DX issue of getting setup. But as you say the backend MUST be hardcoded (without some hacking) and therefore it must be created as a two step process where the first step is running on local (or some other backend other than the one you're configuring). It's a shame really... I imagine at some point this will get addressed. Glad you were able to follow through the tutorial though! At least the explanation wasn't terrible ! 😂
Ah yeah hope that gets addressed at some point. Great tutorial and it was quite clear :)