remove Taskotron-related files #55

Closed
kparal wants to merge 0 commits from taskotron-eol into master
Contributor

Taskotron is now EOL. This tries to remove all relevant files.


Please don't merge this yet, this needs review. @tflink, can you please review this?

I had no idea how to change these files:

playbooks/include/proxies-reverseproxy.yml
playbooks/include/proxies-websites.yml

These machines should be nuked afterwards:

taskotron-dev01.qa.fedoraproject.org
taskotron-stg01.qa.fedoraproject.org
taskotron01.qa.fedoraproject.org
qa10.qa.fedoraproject.org
qa11.qa.fedoraproject.org
qa12.qa.fedoraproject.org
qa13.qa.fedoraproject.org
Taskotron is now EOL. This tries to remove all relevant files. ---- Please don't merge this yet, this needs review. @tflink, can you please review this? I had no idea how to change these files: ``` playbooks/include/proxies-reverseproxy.yml playbooks/include/proxies-websites.yml ``` These machines should be nuked afterwards: ``` taskotron-dev01.qa.fedoraproject.org taskotron-stg01.qa.fedoraproject.org taskotron01.qa.fedoraproject.org qa10.qa.fedoraproject.org qa11.qa.fedoraproject.org qa12.qa.fedoraproject.org qa13.qa.fedoraproject.org ```
Contributor

Metadata Update from @kevin:

  • Request assigned
**Metadata Update from @kevin**: - Request assigned
Author
Contributor

Please note that some files were already removed in b2718b308a.

Please note that some files were already removed in b2718b308a64aa1fb80.
Contributor

@kparal do you want to try to rebase this PR?

@kparal do you want to try to rebase this PR?
Author
Contributor

@tflink has been doing some changes behind the scenes, so I don't want to waste my time. I'm happy to rebase once Tim says it's the right time to do so. Or he can handle it himself, if he prefers. I'm not really sure all the changes in this PR are correct.

@tflink has been doing some changes behind the scenes, so I don't want to waste my time. I'm happy to rebase once Tim says it's the right time to do so. Or he can handle it himself, if he prefers. I'm not really sure all the changes in this PR are correct.
Contributor

I ended up duplicating the work that @kparal did here in PR #107 and it was easier for me to update that PR than this one so I'm going to close it - the issue it was meant to address has now been fixed.

I ended up duplicating the work that @kparal did here in PR #107 and it was easier for me to update that PR than this one so I'm going to close it - the issue it was meant to address has now been fixed.
Contributor

Pull-Request has been closed by tflink

Pull-Request has been closed by tflink

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/ansible#55
No description provided.