Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests: Use inmemory provider backed managed zones #658

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

mikenairn
Copy link
Member

@mikenairn mikenairn commented May 22, 2024

closes #601

Update all DNSPolicy integration tests to use the inmemory provider. If the dns operator is running on the target cluster managedzones and dnsrecords should work as if they are targeting a real DNS Provider.

Requires: Kuadrant/dns-operator#142

@mikenairn mikenairn requested a review from a team as a code owner May 22, 2024 14:36
@mikenairn
Copy link
Member Author

/hold

Will merge after Kuadrant/dns-operator#142

@mikenairn mikenairn force-pushed the inmemory_managed_zones branch 2 times, most recently from 73d4654 to 36c4fd5 Compare May 29, 2024 10:12
@philbrookes
Copy link
Contributor

does this need an unhold? Why are the integration tests being skipped?

@mikenairn
Copy link
Member Author

does this need an unhold? Why are the integration tests being skipped?

Test are doing weird things for some reason, triggered them again. Hold did nothing, prow isn't even enabled on this repo.

@mikenairn mikenairn force-pushed the inmemory_managed_zones branch 2 times, most recently from ef9b749 to 43c5713 Compare June 4, 2024 14:05
Update all DNSPolicy integration tests to use the inmemory provider. If
the dns operator is running on the target cluster managedzones and
dnsrecords should work as if they are targeting a real DNS Provider.

Enable aws, google and inmemory providers in local deployment of dns
operator.
@mikenairn mikenairn merged commit fbd8969 into Kuadrant:main Jun 10, 2024
18 checks passed
@mikenairn mikenairn deleted the inmemory_managed_zones branch June 10, 2024 08:08
dlaw4608 pushed a commit to dlaw4608/kuadrant-operator that referenced this pull request Jun 17, 2024
Update all DNSPolicy integration tests to use the inmemory provider. If
the dns operator is running on the target cluster managedzones and
dnsrecords should work as if they are targeting a real DNS Provider.

Enable aws, google and inmemory providers in local deployment of dns
operator.
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.

DNSPolicy: Update integration tests to use inmemory dns provider
2 participants