Convert Publisher yaml to classic pipeline

Open
#755 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
api, devops

Research direction

Start by reproducing the command using the classic release pipeline, the publisherPath, artifactPath/configuration.extractor.yaml, and the jwttesttoken argument described in the issue. Done means a valid three-part JWT reaches the APIOps Publisher without the format error and the artifacts are published to APIM.

Written by the indexing model from the issue text.

Description

Release version

ApiOps v6.0.1.7

Question Details

Subject: Issue with JWT Token Handling in APIOps Publisher Pipeline

Description: As my Organization has restrictions in creating Yaml pipelines at release level. I am trying to create a classic release pipeline for publisher pipeline .We are encountering an issue where the APIOps Publisher pipeline does not correctly handle the JWT token. Even after hardcoding a valid JWT token, the execution fails with the following error:
JWT is not well formed, there are no dots (.).
The token needs to be in JWS or JWE Compact Serialization Format.

Troubleshooting Steps Taken:

Verified that the JWT token is correctly formatted (three parts separated by dots).
Printed the token before execution to confirm correct passing.
Removed unnecessary quotes while passing the token in the command.
Expected behavior

The APIOps Publisher should accept the valid JWT token without throwing a format error and publish the artifacts to APIM

Actual behavior

The tool incorrectly reports that the token is not well-formed, preventing execution.

Reproduction Steps
Download and extract the latest APIOps Publisher tool.
Define a valid JWT token with three parts (header.payload.signature).
Execute the following command:& "$publisherPath" --config "$artifactPath/configuration.extractor.yaml" --token $jwttesttoken

The process fails, stating that the JWT token is not well-formed.

Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.