APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
MIT License
Bot releases are visible (Hide)
Published by github-actions[bot] about 1 month ago
Full Workspace Support:
This release introduces support for all ApiOps-compatible artifacts within workspaces. If an artifact is supported by ApiOps and exists in a workspace, it is now fully supported.
Note: Workspace resources that are not compatible with ApiOps, such as certificates and other non-supported resources, are also excluded in workspaces for consistency.
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.2-alpha.1.0.2...v6.0.2-alpha.1.0.3
Published by github-actions[bot] about 2 months ago
Added support for extracting more workspaces artifacts. Still work in progress but we are getting cloe.
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.1.1...v6.0.2-alpha.1.0.2
Published by github-actions[bot] 2 months ago
Published by github-actions[bot] 3 months ago
Optimize resource name filtering in extractor #610
Full Changelog: https://github.com/Azure/apiops/compare/v5.1.4...v6.0.1
Published by github-actions[bot] 3 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.2-alpha.1.0.0...v6.0.1-rc2
Published by github-actions[bot] 3 months ago
💥 Not Ready for production yet. Please utilize v6.0.1-rc1 while we march towards complete workspaces support.💥
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.1-rc1...v6.0.2-alpha.1.0.1
Published by github-actions[bot] 3 months ago
💥 Not Ready for production yet. Please utilize v6.0.1-rc1 while we march towards complete workspaces support.💥
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.1-rc1...v6.0.2-alpha.1.0.0
Published by github-actions[bot] 3 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-rc1...v6.0.1-rc1
Published by github-actions[bot] 4 months ago
💥 Please note that this is a breaking release. Its important you read all the release notes below before you adopt it in your environment.💥
💥 Please note that this release requires updating your Gtihub extractor and publisher workflows💥
💥 Please note that this release requires updating your Azure DevOps or Github Pipelines💥
💥 Please note that this release alters the way we release the assets hosted within each release. 💥
apiA
, subscriptions tied to apiB
will not be extracted.In v5, releases are naked executables. You can just download them and run them.
In v6, the releases are zip files. You now have to download the zip file, extract that file to a folder, and run the executable inside the folder. We have updated our ADO and GitHub pipelines to do this, but if you're migrating from v5 to v6, you will need to do this as well.
In v5, the publisher assumes Git has been installed on the computer. When doing Git-related tasks, it calls the command line with git mycommand
. If Git is not installed, the publisher will fail. Also, Git commands are hard-coded in a manner that's consistent across different OSes.
In v6, we use the Lib2GitSharp .NET library. It's responsible for figuring out the right commands and maintaining consistency across OSes. When the code is compiled, it generates a .dll/.so file that includes the right Git binaries for the OS. No need to have Git-preinstalled, but the publisher executable now relies on having the .dll/.so file present in its folder.
We're changing the folder structure for associated top-level resources. Let's use product APIs as an example.
In v5, productA
associated with apiA
and apiB
will generate the following artifact:
[
{
"name": "apiA"
},
{
"name": "apiB"
}
]
In v6, the structure looks like this:
Here are the affected resource types:
See the discussion here.
This release includes support for product subscriptions. When you extract your subscription, the file artifacts/subscriptions/yoursubscription/subscriptionInformation.json
will include the subscription owner in properties.ownerId
.
If you then promote that subscription to a higher environment, the publisher will likely fail as properties.ownerId
references a user ID in the lower environment.
To get around this, override your configuration file with the desired owner in the higher environment. A sample configuration file would be:
subscriptions:
- name: mysubscription
properties:
ownerId: /users/userId
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1.0.1...v6.0.0-rc1
Published by github-actions[bot] 4 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.10
Published by github-actions[bot] 4 months ago
💥 Not Ready for production yet. Please use v5.x for production💥
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.9
Published by github-actions[bot] 5 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.8
Published by github-actions[bot] 5 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.7
Published by github-actions[bot] 5 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.6
Published by github-actions[bot] 5 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.5
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v6.0.0-alpha.1...v6.0.0-alpha.1.0.1
Published by github-actions[bot] 6 months ago
Full Changelog: https://github.com/Azure/apiops/compare/v5.1.4...v6.0.0-alpha.1