Issue #500: Do not store personal copr-cli token in sanity tests - copr

copr / copr

#500 Do not store personal copr-cli token in sanity tests

Closed 5 years ago by frostyx. Opened 5 years ago by frostyx.

When this command

/root/copr/beaker-tests/Install/Config-copr-cli/runtest.sh

is executed in the DockerTestEnv container, it generates ~/.config/copr with personal token.

We should add non-FAS beakertest user into our copr-fe-dev database and use it in our tests.

Edit: To specify, it doesn't generate the personal token from your host system - this would IMHO also be a fine solution. No, we actually store a personal token in git.

frostyx commented 5 years ago

Modified in PR#591

praiskup commented 5 years ago

We should add non-FAS

Why non-FAS? That means that you can not log-in via user interface as that user, which might be useful sometimes.

frostyx commented 5 years ago

Why non-FAS? That means that you can not log-in via user interface as that user, which might be useful sometimes.

FTR - We haven't added any user, see the PR#591

Merged, closing.

Metadata Update from @frostyx:
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

None

Milestone

None

blocked

None

copr / copr

Source Code

Documentation

#500 Do not store personal copr-cli token in sanity tests Closed 5 years ago by frostyx. Opened 5 years ago by frostyx.

Metadata

#500 Do not store personal copr-cli token in sanity tests

Closed 5 years ago by frostyx. Opened 5 years ago by frostyx.