guythetechie

Results 98 comments of guythetechie

Yes, please go ahead and try the latest v7 alpha code. If it's easier to use executables instead of cloning the repo, you can find the latest alpha release [here](https://github.com/Azure/apiops/releases)....

@anotherRedbeard - [here](https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-log-event-hubs?tabs=bicep#logger-with-connection-string-credentials) is the expected configuration for event hub credentials. It shows various options for connection strings, system-assigned managed identities, and user-assigned managed identities. Also, as you've noted, the...

@anotherRedbeard - when you run the extractor, the `apiVersionSetId` property in your `apiInformation.json` has the full resource ID of your version set. That resource ID maps to your original APIM...

@jblaaa-codes & @samuelchong - I would suggest doing the following: - Set up your federated credentials - In your GitHub action workflow, add a step to log on to Azure...

@fabienmazieres - are you passing the full path of `configurationd1.yaml` to the publisher? You can see how it's defined in our starter [ADO](https://github.com/Azure/apiops/blob/7796fefc7973e4c3eea6a1bef5e8fa2b82f93b8a/tools/azdo_pipelines/run-extractor.yaml#L157) and [GitHub](https://github.com/Azure/apiops/blob/7796fefc7973e4c3eea6a1bef5e8fa2b82f93b8a/tools/github_workflows/run-extractor.yaml#L100) pipelines.

@fabienmazieres - after rereading your issue, I think there's a misunderstanding of how the extractor and publisher work with configuration. - The extractor configuration file specifies which resources should be...

@fabienmazieres - I don't think so. It's not a simple task, and it goes against our philosophy of Git being the source of truth. If different teams are responsible for...

@psvn - I would suggest [enabling trace logging](https://github.com/Azure/apiops/wiki/Logging). It will show the contents of the API calls to update your WSDL APIs. If your properties get overwritten unexpectedly, you can...

@xuhongl - just pushed an update to [this branch](https://github.com/Azure/apiops/tree/v6.0.2) that supports additional workspace artifacts. We'll create a preview release soon, but in the meantime, you can always clone that branch...