ratify-project/ratify

test: Ratify repo move validation

Closed this issue · 7 comments

susanshi commented

What would you like to be added?

We are moving Ratify repository to a new home. This issues will document the areas and result of validation.

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this feature?

  • Yes, I am willing to implement it.
susanshi commented

A test repo move has been performed to validate the impact:

Ratify Installation

Active Links

Broken links

Action Items

  • Update doc links to point to new repo path
  • republish previous release of ratify ghcr images to new path if needed
  • inform partners about repo move to update helm chart url
  • review and installation guide from ratify blogs for azure /AWS / vanifi.
  • review installation steps from ratify playground
  • update artifact hub

Ratify Plugins Authoring

Transferred Items

Action Item

  • In 1.3 we will remodule, we will release doc for plugin authors to update import to target the updated ratify path

Dev workflows

Transferred Items

  • Branches/tags/Issues/PRs/Discussions/Milestones were transferred
  • Secrets content were copied

Action Item

  • Review github workflow status after repo move
  • Run one off workflows including publish quick start samples
  • New PAT maybe required to performs actions on the new repository
susanshi commented

Adding checklist from @akashsinghal to see if we have answers to all items:
Ratify Repository Transfer Open Questions

  • Ratify Packages

  • Are existing binaries published still accessible via old repo path?

  • Will existing binary assets automatically publish under new repository?
    - Ratify's module is current github.com/deislabs/ratify. When do we plan to update this? For previously published packages visible in pkg.go.dev, do we need to take steps so user's can find future versions under the new repo path? If we update the module name, will it break out-of-tree plugins that import it?

  • Ratify Registry Artifacts

  • Are existing images still accessible via ghcr.io/deislabs/ratify?

  • Do all existing artifacts transfer to new repo?

  • Ratify Helm Charts

  • Do we need to re release our helm charts with an updated CRD + core ratify images?

  • Do we need to update artifact hub?

  • Ratify github published page

  • The helm chart is published to repo's github pages. Will the existing helm charts at deislabs.github.io still be accessible?

  • Ratify Github Actions

  • Will the repo transfer re trigger releases? As in when the new tags come over, will they count as tag push events that will trigger are auto release workflows?

  • Do any release actions have hardcoded dependency on deislabs/ratify?

  • Do we need to update the helm publishing action to point to a new github.io page?

  • Ratify Website

  • Do we need to update all links referencing deislabs/ratify or will github redirect to new repo location?

  • Do we need to make any updates to the GH action that auto publishes new main branch changes to website?

  • Tokens

  • Do we need to regenerate tokens for GH actions?

  • CRDs (not blocking)

  • The Ratify CRDs are pinned to the group config.ratify.deislabs.io. What is the plan to migrate?

susanshi commented

Review github action workflow status after repo move. Adding action item: after repo move, run workflow to publish quick start sample , we should review the sample image for the built in cosign plugin

susanshi commented

Action item: Update artifact hub after repo move

susanshi commented

Review: interactive ratify playground experience

susanshi commented

Action: inform partners about repo move, update blogs links if needed.

susanshi commented

Discussed from community meeeting, we should publish our chart to doc site in the future.