Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Fixing tests using consul for dns #232

Merged

Conversation

anouarchattouna
Copy link
Contributor

  • Refactoring tests
    • Add a new test stage initialize_unseal useful when running multiple times the validation stage against the same cluster
    • Add testVaultUsesConsulForDns for all test cases
  • Updating vault service configuration
    • Adding service_registration used when using a different storage backend like s3
    • Updating systemd configuration based on this configure-systemd documentation
  • Bumping versions
    • bump min_packer_version -> 1.5.4
    • bump vault_version -> 1.6.1
    • bump consul_version -> 1.9.2

bump 'min_packer_version' -> 1.5.4
bump 'vault_version' -> 1.6.1
bump 'consul_version' -> 1.9.2
Adding 'service_registration' used when using a different storage backend like 's3'
Updating systemd configuration based on this documentation https://learn.hashicorp.com/tutorials/vault/deployment-guide\#step-3-configure-systemd
Add a new test stage 'initialize_unseal' useful when running multiple times the 'validation' stage against the same cluster
Add 'testVaultUsesConsulForDns' for all test cases
Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

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

Very nice, thanks! Just some minor NITs, and then I can kick off tests.

modules/run-vault/run-vault Outdated Show resolved Hide resolved
modules/run-vault/run-vault Show resolved Hide resolved
test/vault_helpers.go Outdated Show resolved Hide resolved
Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

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

This looks great, thank you! I'll kick off tests now.

Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

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

Thanks! Just one comment and then I can kick off tests.

modules/run-vault/run-vault Outdated Show resolved Hide resolved
Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

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

Thanks! I'll kick off tests.

@brikis98
Copy link
Collaborator

Tests passed! 🎉

So does this imply there's no actual bug with #228 / Ubuntu 18.04? That it was just that the service wasn't being registered? Or did we need newer Consul / Vault versions?

@anouarchattouna
Copy link
Contributor Author

Tests passed! 🎉

So does this imply there's no actual bug with #228 / Ubuntu 18.04? That it was just that the service wasn't being registered? Or did we need newer Consul / Vault versions?

Indeed, it resolves #228 by adding the service registration and using newer Consul / Vault versions

@brikis98
Copy link
Collaborator

Tests passed! 🎉
So does this imply there's no actual bug with #228 / Ubuntu 18.04? That it was just that the service wasn't being registered? Or did we need newer Consul / Vault versions?

Indeed, it resolves #228 by adding the service registration and using newer Consul / Vault versions

Sorry, crazy week, just coming back to this now. That's great news, thank you! I'm going to merge and release this now.

@brikis98 brikis98 merged commit f1ac700 into hashicorp:master Feb 16, 2021
@brikis98
Copy link
Collaborator

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants