Replace yaml scopes by regular standards - #1199
Conversation
3a6aea8 to
ac201ed
Compare
|
Any clue why the link checks are failing here? |
|
@jklare Not really. The links do work. Maybe the docs page is defending itself against bots :) |
b84ff70 to
2d6babb
Compare
jklare
left a comment
There was a problem hiding this comment.
LGTM, thanks for pushing this. I think this is a lot easier to understand when trying to figure out which tests need to pass and what the difference between each of the scope version is. I added a couple of questions and comments.
e4182e6 to
09a2044
Compare
|
This should probably be rebased before being merged. |
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
f0334ee to
9ca87ac
Compare
|
Unfortunately, we did not consider that the links to the old Scope pages are no longer available and therefore result in a 404 error.
I can update the links on https://sovereigncloudstack.org. However, I have used these URLs in numerous places over the past few months and have also shared them via email etc. which I cannot or do not want to change. Since I am a supporter of "Cool URIs don’t change", I will try to fix this with "plugin-client-redirects" to redirect the old links to the new ones. |
Resolves #1198
This is meant as a preview of a quite radical change. It's possible that multiple PRs would be needed to be in line with extant regulations.