Add a cleanup step for bootstrapper files to remove stale NUKE_ENTERPRISE_TOKEN handling#519
Add a cleanup step for bootstrapper files to remove stale NUKE_ENTERPRISE_TOKEN handling#519ITaluone wants to merge 2 commits into
NUKE_ENTERPRISE_TOKEN handling#519Conversation
ebdf1a6 to
397e7ed
Compare
1d801f3 to
3e94c3f
Compare
|
@dennisdoomen Should this go into the already existing |
I would definitely make that a dedicated step. |
|
Cool :) |
b361254 to
e2cbe24
Compare
|
Should now fit definitely :) |
ITaluone
added
enhancement
e2cbe24 to
7c062b2
Compare
| return Task.CompletedTask; | ||
| } | ||
|
|
||
| internal static RewriteResult Cleanup(string content) |
There was a problem hiding this comment.
🔧 We don't want to test the implementation details of a step. Instead, we use the public API of this class.
🌱 (planting a seed) In principle testing the step directly is wrong as well. We should really be using the Migration class as the subject.
There was a problem hiding this comment.
Do I got this correct, that the one integration test would suffice then?
There was a problem hiding this comment.
I cannot see a way to not test the actual internals, without bloating this PR.
Should we for now proceed with this and refactor the tests later?
There was a problem hiding this comment.
What I meant is that for now, we should always use the public API of that step, and that is not that internal Cleanup.
7c062b2 to
5c1845b
Compare
…PRISE_TOKEN` handling
5c1845b to
c1fa6e4
Compare
3 participants
Closes: #518
Add a small cleanup step, which removes stale env var check for the
NUKE_ENTERPRISE_TOKENvariable, which in return adds a special nuget source (which at best is stale and at worst non-existent).