wso2 / wso2/docs-apim

Doc Feedback: Need clearer details about how to migrate from apim 4.2. to apim 4.5

Open
#9,789 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
99
Forks
708
Avg merge
1d 7h
Merged PRs (30d)
22

Description

Location : https://apim.docs.wso2.com/en/latest/install-and-setup/upgrading-wso2-api-manager/upgrading-api-manager/
APIM 4.5.0

Note on page:
If you are upgrading from WSO2 API Manager 4.2.0 to 4.5.0, you can experience a seamless product upgrade with no data migration. This pivotal change facilitates a smooth transition for current API Manager 4.2.0 users to the latest version, eliminating the need for complex migrations.

Problem:
We don't indicate how to achieve this. It "sounds like" that customers need to just install APIM 4.5 on top of 4.2. But is the migration script required? (Internal migration documentation review indicates that a migration is required but the old migration script/jar approach is not required now.)

Reason for this issue to be raised:
Customer Success case asking for further clarification about how to achieve this.

Additionally with the profile change a formal migration/transition is required if customer is not on an all-in-one deployment.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the upgrading API Manager page linked in the issue and review the APIM 4.2.0 to 4.5.0 guidance. Clarify whether a migration step is required, how the profile change affects non-all-in-one deployments, and what customers should do; the page is done when these transition steps are explicit.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.