I have a proxy deployed on two revisions: revision 6 with the base path api/v1, and revision 10 with the base path room_reservation.
However, when I downloaded the 6th revision and opened the XML file, I found the base path set as room_reservation, which is incorrect.
These two statements are in conflict. If your revision 6 has basepath /api/v1 , and then you download that revision and the downloaded bundle shows a basepath of /room_reservation , then... the first statement is not true, as far as Apigee is concerned. The downloaded bundle is the truth as far as Apigee is concerned.
This mismatch is affecting my CI/CD pipelines.
Mismatch, hmmmm.... I think you just need to use the correct basepath in the bundles that you process through ci/cd. I don't see any evidence of a mismatch - in other words, no evidence that Apigee is telling you two conflicting things. There might be a mismatch between what you think should be there, and what is actually there. But that's a process and understanding problem, not an Apigee problem.
Any idea how I can retrieve the correct base path for a specific revision?
Yes: just download the bundle as you have done. There is a pitfall in Apigee OPDK: revisions are not immutable. We've modified this on X and hybrid, so that proxy bundle revisions, once dpeloyed, are immutable. But in OPDK you can modify a specific revision, even after it is deployed. Just because you CAN doesn't mean you SHOULD. By doing so you can confuse yourself. To avoid this pitfall, don't modify revisions. When you import a bundle via CI/CD, import a new revision, always.
The fact that you have a revision 10, and it seems like you might be trying to import something into... revision 6? ... that indicates you are running into this anti-pattern.
LinkedIn
Twitter
