Skip to content

Conversation

@LesnyRumcajs
Copy link
Member

@LesnyRumcajs LesnyRumcajs commented Apr 2, 2025

Summary of changes
Changes introduced in this pull request:

  • obliterated remote exec in favour of cloud init
  • cleanups & refactoring

Reference issue to close (if applicable)

Closes #477
Closes #474

Other information and links

@LesnyRumcajs LesnyRumcajs force-pushed the hardcode-dns-sync-check branch 3 times, most recently from b43e142 to bcc2dec Compare April 3, 2025 13:16
@LesnyRumcajs LesnyRumcajs force-pushed the hardcode-dns-sync-check branch from 0c72c46 to 6499d35 Compare April 3, 2025 13:19
@LesnyRumcajs LesnyRumcajs force-pushed the hardcode-dns-sync-check branch 2 times, most recently from 746ce54 to 7baa051 Compare April 9, 2025 12:23
@LesnyRumcajs LesnyRumcajs force-pushed the hardcode-dns-sync-check branch from 16db1ac to 7aa31d9 Compare April 9, 2025 13:09
@LesnyRumcajs LesnyRumcajs marked this pull request as ready for review April 9, 2025 13:11
@LesnyRumcajs LesnyRumcajs requested a review from a team as a code owner April 9, 2025 13:11
@LesnyRumcajs LesnyRumcajs requested review from hanabi1224 and lemmih and removed request for a team April 9, 2025 13:11
Copy link
Contributor

@lemmih lemmih left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@LesnyRumcajs LesnyRumcajs changed the title fix: hardcode dns in sync check deployment fix: cloud init instead of remote exec for sync check Apr 9, 2025
@LesnyRumcajs LesnyRumcajs merged commit dd6af18 into main Apr 9, 2025
9 checks passed
@LesnyRumcajs LesnyRumcajs deleted the hardcode-dns-sync-check branch April 9, 2025 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deployments should use cloud init instead of remote provisioner Deployment fails in timeout

4 participants