Importing cortextool from separate repo cortex-tools

[simonswine]

This is an automated import of the https://github.com/grafana/cortex-tools repo.

For preparing the remote repo this script was used:

#!/usr/bin/env bash

CHECKOUT_PATH=$(mktemp -d $TEMPLATE)

git clone git@github.com:grafana/cortex-tools.git "${CHECKOUT_PATH}"

cd $CHECKOUT_PATH
git filter-repo \
  --filename-callback '
if filename.startswith(b"vendor/") or filename in [b"go.mod", b"go.sum"]:
  return None
if filename.startswith(b"cmd/"):
    if filename.startswith(b"cmd/cortextool"):
        return filename
    else:
        return None
return b"cmd/cortextool/" + filename
' --message-callback '
import re
return re.sub(b"#([0-9]+)", b"https://github.com/grafana/cortex-tools/pull/\\1", message)
'
# replace import paths
git ls-files '**/*.go' | xargs sed -i 's#github.com/cortexproject/cortex#github.com/grafana/mimir#g'
git ls-files '**/*.go' | xargs sed -i 's#github.com/grafana/mimir/pkg/cortex#github.com/grafana/mimir/pkg/mimir#g'
git ls-files '**/*.go' | xargs sed -i 's#github.com/grafana/cortex-tools#github.com/grafana/mimir/cmd/cortextool#g'
git ls-files '**/*.go' | xargs sed -i 's#github.com/prometheus/prometheus/pkg/#github.com/prometheus/prometheus/model/#g'
git ls-files '**/*.go' | xargs sed -i 's#github.com/prometheus/alertmanager/pkg/#github.com/prometheus/alertmanager/model/#g'
git commit -m "Change import paths" .

This fixes https://github.com/grafana/mimir-squad/issues/437

[simonswine]

I think I have addressed most issues that have arisen:

• Removed Loki reference of ruler CLI.
• Removed unused code paths of repo (e.g. bench, chunktool and overrides-exporter)

The ones remaining are:

• Rename the command itself, once there is some clarity which name will be chosen
• Will the CLI be Apache 2 or AGPL?

[pracucci]

Do we wanna keep using it? I didn't have a very nice experience with that. I'm wondering if we can release using Mimir tooling.

[simonswine]

I have not found to many issues when releasing, but I think we should have something that is run in a more automated fashion than cortex-tools had.

I think we should address this in a separate PR and have created #747

[pracucci]

I would move cmd/cortextool/pkg to pkg/cortextool (or whatever the name will be)

[simonswine]

I would like to deffer that to the time when we have a name.

[simonswine]

I think it makes sense to merge this state and work on the remaining work in separate PRs:

• renaming
• release automation
• integration of documentation from README.md to docs/

[pracucci]

I think it makes sense to merge this state and work on the remaining work in separate PRs:

I agree. Could you rebase to fix confclits, so we can merge, please?

[pracucci]

This PR must be merged WITHOUT squashing (just a merge commit).