Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pick a source of truth for auth.yaml, implement it into the multiregion test #2623

Closed
Neon-White opened this issue Aug 3, 2020 · 1 comment
Closed

Pick a source of truth for auth.yaml, implement it into the multiregion test #2623

Neon-White opened this issue Aug 3, 2020 · 1 comment
Labels
High Priority High priority issues

Comments

@Neon-White
Copy link
Member

Right now, OCS-CI has two possible for auth.yaml -

  1. From the local code runner, under ocs-ci/data/auth.yaml
  2. From OCS-QE's private AWS bucket, where the file is then loaded into OCS-CI's config.

This is confusing, hard to manage, and may result in unexpected behaviors.
@Neon-White Neon-White added the High Priority High priority issues label Aug 3, 2020
This was referenced Aug 9, 2020
Closed
Closed
Merged
@Neon-White
Copy link
Member Author

Neon-White commented Jun 14, 2022 •
edited

Was addressed in #2664, I don't think there's a reason to try and maintain just one source - having both options has its uses and is convenient

@Neon-White Neon-White closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
High Priority High priority issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Neon-White