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

Update transition script to allow docker/podman usage #4427

Merged
merged 33 commits into from
Oct 17, 2022

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Oct 15, 2022

#4423 is required to merge before this does, hence draft. Resolves #4386

This PR updates the transition script to...

  • No longer use temp directory because breadcrumbs are available now.
  • Allows the transition script to use docker or podman for their transition script run.

TODO:

  • Update transition script readme

@scbedd scbedd self-assigned this Oct 15, 2022
@scbedd scbedd requested a review from JimSuplizio October 15, 2022 02:30
@scbedd scbedd changed the title Update transition script to update Update transition script to allow docker/podman usage Oct 15, 2022
@scbedd scbedd marked this pull request as ready for review October 17, 2022 20:29
@scbedd scbedd requested a review from mikeharder as a code owner October 17, 2022 20:29
## Setup

Before running the script, understand that **only services that have migrated to use the `test-proxy` as their record/playback solution can store recordings into the external assets repository.** The CLI command commands are invoked from the `test-proxy` itself, so if it is NOT being used for record/playback, the work to transition to the `test-proxy` must be done before recordings can be moved.
Before running the script, understand that **only services that have migrated to use the `test-proxy` as their record/playback solution can store recordings into the external assets repository.** The test-proxy itself contains the code for `restoring`/`push`ing recordings, so if it is NOT being used for record/playback, that work must be completed before recordings can be moved.
Copy link
Member

Choose a reason for hiding this comment

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

I think the code blocks are confusing here, because restoring is not a test proxy verb. Maybe just remove them, or an alternative?

Suggested change
Before running the script, understand that **only services that have migrated to use the `test-proxy` as their record/playback solution can store recordings into the external assets repository.** The test-proxy itself contains the code for `restoring`/`push`ing recordings, so if it is NOT being used for record/playback, that work must be completed before recordings can be moved.
Before running the script, understand that **only services that have migrated to use the `test-proxy` as their record/playback solution can store recordings into the external assets repository.** The test-proxy itself contains the code for restoring/pushing recordings (`test-proxy [restore|push]`). If it is NOT being used for record/playback, that work must be completed before recordings can be moved.

Co-authored-by: Ben Broderick Phillips <ben@benbp.net>
@scbedd
Copy link
Member Author

scbedd commented Oct 17, 2022

/check-enforcer evaluate

1 similar comment
@scbedd
Copy link
Member Author

scbedd commented Oct 17, 2022

/check-enforcer evaluate

@scbedd
Copy link
Member Author

scbedd commented Oct 17, 2022

/check-enforcer override

@scbedd scbedd merged commit 86cad9e into Azure:main Oct 17, 2022
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.

Add podman and docker support to the transition script
3 participants