axway / agents-mulesoft Goto Github PK

Provide an option in the config yaml file to authenticate with the Org/Environment Client ID & Secret pair.

Maintain existing authentication method with the username and password.

Is your feature request related to a problem? Please describe.
A changelog has not been added to the project. Adding a changelog with a list of all the items that changed for a new release will help document what is being added to the project, and it will also help identify any breaking changes.

Describe the solution you'd like

• Add a CHANGELOG.md file.
• Add automation to the pipeline so that when a commit is added to main, the changelog is automatically updated to reflect what that change is.
• Consider a commit message format to easily identify what the change is, and who made it.

Describe the bug

Unable to view RAML API created in Mulesoft in Amplify Service Registry

To Reproduce

1. Export an existing API running in the MuleSoft platform in RAML format
2. Create a new API based on that RAML API, importing that file as the backend API
3. Deploy

Expected behavior

API should be visible in Amplify Service Registry

Logs

{"apiAssetVersion":"1.0.0","apiID":18864163,"assetID":213012514,"assetName":"new-raml-api","level":"error","message":"error getting the service details: invalid character 'P' looking for beginning of value","time":"2023-07-31T08:12:41-07:00"}

Version
CentOS Linux release 7.9.2009
MuleSoft agent 1.1.23

Additional context

This has replicated in two different environments.

Apparently, the agent get API spec from MuleSoft and converts it from YAML to JSON. MuleSoft's GUI has different options for the "Download" actions for OAS and RAML APIs and appears to download to providing RAML. We might have to call MuleSoft differently to get the desired API representation.

It looks like, that the Mulesoft Traceability Agent YAML-File is incorrect. It looks like the default from the SDK.

https://github.com/Axway/agents-mulesoft/blob/main/mulesoft_traceability_agent/mulesoft_traceability_agent.yml

Can someone perhaps check?

Today, we deliver agents as binary and it is not easy to know which distribution to select.

The goal is to deliver agents as Docker image that can be run from any Docker environment.

When calling UpdateStateWithProperties, description is required.

Currently amplify mulesoft agent discovers active and unregistered and inactive APIs from mulesoft anypoint platform.

A LICENSE file is needed that contains the contents of the ASF license.
A copyright statement is needed at the top of each file.

This is to facilitate compliance to this issue

Is your feature request related to a problem? Please describe.
Our contributing code of conduct has not been defined yet.

Describe the solution you'd like
A CODE_OF_CONDUCT.md file should be added to describe how contributors should interact with each other in discussions on this project.

this is fake

Write a CONTRIBUTION.md file to define how contributors are meant to add code to the project.

When a mulesoft API is discovered to have multiple instances for a single version, we should group the mulesoft instances under a single API Service Instance that contains a list of all the endpoints, and that Instance should be linked to a single API Service Revision.

Is your feature request related to a problem? Please describe.
A security policy has not been defined.

Describe the solution you'd like
A SECURITY.md file should be added to describe how contributors are meant to report security issues.

Describe the bug
When the discovery agent pull APIs there is an error on policies retreive

Logs
{"component":"httpClient","duration(ms)":488,"id":"d9c0d586-e902-44ea-ad2b-c5747bd27135","level":"trace","message":"request succeeded","method":"GET","package":"sdk.api","received(bytes)":15,"status":200,"time":"2023-11-15T15:30:17+01:00","url":"https://anypoint.mulesoft.com/apimanager/api/v1/organizations/b4bce7ea-970a-4376-88e1-8c76f3723c67/environments/aafd1b9a-880f-4c68-a9ad-7986feb8fbee/apis/19111417/policies?masterOrganizationId=b4bce7ea-970a-4376-88e1-8c76f3723c67"}
{"apiAssetVersion":"1.0.0","apiID":19111417,"assetID":213106262,"assetName":"petstore-demo","level":"error","message":"error getting the service details: json: cannot unmarshal object into Go value of type []anypoint.Policy","time":"2023-11-15T15:30:17+01:00"}

** Here the result of the API Request on my mulesoft Environnement **
{
"policies": []
}

Is your feature request related to a problem? Please describe.
Update the contributing guide based on feedback, and make a few small changes to the revision name

Describe the solution you'd like
Some feedback has been provided on the contribution guide that needs to be added.
A couple small changes need to be added for the revision name to align with the sdk.