Epic Goal

• When importing a cluster using autoimport method, do not also show the manual import command on the screen.

Why is this important?

• A smooth onboarding experience for your many existing clusters is needed to ensure that ACM customers can quickly make use of management capabilities.
• Serviceability is necessary for our customers to be able to self service their own problem.
• We do not want to have a confusing user experience with the use of autoimport and manual import methods.

Scenarios

1. Cluster > Import cluster
2. select an auto import method, eg, supply Kubeconfig
3. submit.
4. We DO NOT want the console import wizard to show the user a message that they need to copy a command and run it. This is an auto import flow and no manual command is needed.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• The user should not be offered a manual import command when autoimport is used.
• Cluster status should show as Importing rather than Pending import in the cluster list
• After failed automatic import, the cluster status should show Failed import in the cluster list (not only on cluster details page)

Dependencies (internal and external)

1. https://issues.redhat.com/browse/ACM-1061

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• Y FIPS Readiness
• Y Works in Disconnected
• Y Global Proxy Support
• N/A Installable to Infrastructure Nodes
• Y No impacts to Performance and Scalability
• Y Backup and Restorable