refactor!: gce-container-declaration deprecation#188
Conversation
2f45ee3 to
3e10576
Compare
|
hey @Zurvarian, can you take a look? Let me know if you have any suggestions and whether this works for you 👍 |
|
@d-costa I'll try to give it a try when I'm free (Possibly next week) |
3e10576 to
a1696c0
Compare
|
@d-costa I've tested your fork and it worked fine, thanks! |
|
Thanks for working on this! |
a1696c0 to
c9ee670
Compare
|
@d-costa Thank you for your work 🙏 When testing this change i had to add to the definition of my module. Otherwise terraform would fail with: |
2232206 to
45890e6
Compare
Due to the Compute Engine container startup agent deprecation on July 21 2025, GCP recommends now using a startup script or cloud-init to run containers in VMs. To avoid impacting users that already have startup scripts, this commit uses cloud-init to spin up the container. Changes: - Remove container module - Add service responsible for the Atlantis container - Changed `command` and `args` default values to `[]` instead of null, since we can't iterate null values Impact: - `google_compute_disk.persistent will be updated in-place` - `google_compute_instance_group_manager.default` will be updated in-place` - `google_compute_instance_template.default must be replaced` **Requires a couple minutes of downtime while the VM is restarted.** Sources: - https://cloud.google.com/compute/docs/deprecations/container-startup-agent-on-compute - https://cloud.google.com/compute/docs/containers/migrate-containers Signed-off-by: David Costa <33375428+d-costa@users.noreply.github.com>
45890e6 to
ce608fa
Compare
|
thanks for the heads up @AndreaGiardini, I went ahead and changed the default values to |
|
Let me know if this would rather be discussed on a separate issue than a closed PR, but I have just tried upgrading and after restart the disk is simply not mounted. Same if I create a new instance. I looked everywhere in the module and simply fail to see what is supposed to format and mount the disk. Please ignore me, just found #195 |
Due to the Compute Engine container startup agent deprecation on July 21 2025, GCP recommends now using a startup script or cloud-init to run containers in VMs.
To avoid impacting users that already have startup scripts, this commit uses cloud-init to spin up the container.
Changes:
commandandargsdefault values to[]instead of null, since we can't iterate null valuesImpact:
google_compute_disk.persistent will be updated in-placegoogle_compute_instance_group_manager.default will be updated in-placegoogle_compute_instance_template.default must be replacedRequires a couple minutes of downtime while the VM is restarted.
Sources:
I tested creating and updating from an existing deployment, and it went as expected. Nonetheless, it would be best if someone else could confirm it 😄