letsencrypt / letsencrypt/boulder

Fully move from pardot-test-srv to salesforce-test-srv

Open
#8,410 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.8k
Forks
649
Avg merge
3d 23h
Merged PRs (30d)
24

Description

Due to necessary configuration changes, this is a two-part change:

Part 1:

  • Deprecate config.OAuthAddr in test/pardot-test-srv.go and replace it with config.SalesforceAddr (#8438)
  • Deprecate --oauth-addr in test/pardot-test-srv.go and replace it with --salesforce-addr (#8438)
  • Rename email to salesforce (#8523)
  • Rename email.Exporter proto to salesforce.Exporter (#8523)
  • Rename pardot-test-srv to salesforce-test-srv (#8523)

[!WARNING]
Part 2 cannot begin until IN-12087 has been completed and deployed successfully.

Part 2:

  • Remove oauthAddr from salesforce-test-srv
  • Stop copying salesforce-test-srv as pardot-test-srv

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

First verify that IN-12087 has been completed and deployed successfully, since Part 2 is blocked until then. Review the salesforce-test-srv configuration and the changes in test/pardot-test-srv.go, then remove oauthAddr and stop copying salesforce-test-srv as pardot-test-srv. Done means both unchecked Part 2 items are completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.