Automatic Publishing API-M with Generate #1671
randiratnayake
started this conversation in
General
Replies: 1 comment
-
I have tested my forked repository on this proposed solution: #1675 and it works as expected. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently working on automating the API-M developer portal deployment from one environment to another (Azure DevOps). I have successfully used
scripts.v3/capture.js
to package the snapshot and generate pipeline artifacts.node ./capture --subscriptionId "$(SubscriptionId)" --resourceGroupName "$(ResourceGroupName)" --serviceName "$(ServiceName)"
I use the same artifacts and target different environments with gated approvals to publish the portal changes.
node ./generate --subscriptionId "$(AzureSubscriptionId)" --resourceGroupName "$(ResourceGroupName)" --serviceName "$(ServiceName)" --folder "$(Pipeline.Workspace)/snapshot"
But there is no option to publish the changes. Digging around, I see
scripts.v3/migrate.js
has a built-in publish method. I wonder can't we have an optional parameter for thegenerate
script so that it also publishes if the flag is set. Any limitations for not doing it?Beta Was this translation helpful? Give feedback.
All reactions