tooling - add VCR support to acceptance testing#32034
Conversation
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Note to reviewer: Failure in deprecated functionality check is a false-positive, this line has not been touched. |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
|
Build failure This pull request contains a build failure which needs addressed here . |
partially working, found limitation in requests containing id derived IDs reworked the recorder, folded in polling changes and completed data redactions for subscription IDs patch up signalling for explicit record and replay modes add vcr testing guide
sreallymatt
force-pushed
the
f/go-vcr-enablement
branch
from
7eafec5 to
c5edce2
Compare
|
Build failure This pull request contains a build failure which needs addressed here . |
4 participants
Community Note
Description
This PR introduces VCR-based testing to the AzureRM provider. By recording and replaying the HTTP interactions between the Provider and the Azure API we can speed up our test suite, reduce costs, enable offline test execution, and ensure deterministic, reproducible test runs without needing live Azure resources every time.
WIP: Technical discussions are in progress that will decide some additional implementation details here.
NB: picked up some unrelated vendoring due to basing on later version of
go-azure-sdkthis will resolved when hashicorp/go-azure-sdk#1308 is merged and the provider bumped so this PR can be rebased.Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
tooling- Add support for VCR based acceptance testingThis is a (please select all that apply):
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the provider.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Note
If this PR changes meaningfully during the course of review please update the title and description as required.