Skip to content

move RFC2136 DNS01 tests to test/integration#4730

Merged
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:movednstest
Jan 13, 2022
Merged

move RFC2136 DNS01 tests to test/integration#4730
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:movednstest

Conversation

@SgtCoDFish
Copy link
Copy Markdown
Member

Since this test requires setup before it can successfully run, we define it as an integration test and move it here so that on a fresh checkout a user can always run go test ./pkg/... and expect that it would succeed.

Also:

  • tweaks some comments
  • adds methods for getting nameserver / tsig algorithm from DNSProvider

/kind cleanup

NONE

Since this test requires setup before it can successfully run,
we define it as an integration test and move it here so that on a
fresh checkout a user can always run `go test ./pkg/...` and expect that
it would succeed.

Also:

- tweaks some comments
- adds methods for getting nameserver / tsig algorithm from DNSProvider

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
@jetstack-bot jetstack-bot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. area/acme Indicates a PR directly modifies the ACME Issuer code area/acme/dns01 Indicates a PR modifies ACME DNS01 provider code area/testing Issues relating to testing approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 12, 2022
Copy link
Copy Markdown
Contributor

@irbekrm irbekrm left a comment

Choose a reason for hiding this comment

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

This makes sense, I've ran go test ./pkg/... from this branch and the only test failing was the versionchecker one.
Thanks for improving the comments!

I guess at some point we may want to update the contributing docs with more info about testing strategy (everything with dependencies in integration tests) and how to run the different tests, but that may make more sense once the bazel -> make migration is done

/lgtm

@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2022
@jetstack-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, SgtCoDFish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@SgtCoDFish
Copy link
Copy Markdown
Member Author

but that may make more sense once the bazel -> make migration is done

Great minds think alike 😁 It's on my roadmap to do this after the migration, yeah 👌

@SgtCoDFish SgtCoDFish mentioned this pull request Jan 13, 2022
30 tasks
@jetstack-bot jetstack-bot merged commit f1813d0 into cert-manager:master Jan 13, 2022
@jetstack-bot jetstack-bot added this to the v1.7 milestone Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/acme/dns01 Indicates a PR modifies ACME DNS01 provider code area/acme Indicates a PR directly modifies the ACME Issuer code area/testing Issues relating to testing dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants