infra/otc-metadata
16
0
Fork 13
Code Issues 5 Pull Requests 1 Packages Releases Wiki Activity

New service - UCS - Ubiquitous Cloud Native Service #310

Open
oeotvos wants to merge 3 commits from oeotvos/otc-metadata:main into main
pull from: oeotvos/otc-metadata:main
merge into: infra:main
Conversation 6 Commits 3 Files Changed 3 +38
oeotvos commented 2025-05-27 11:57:33 +00:00
Contributor
Copy Link
oeotvos added 1 commit 2025-05-27 11:57:33 +00:00
New service - UCS
All checks were successful
gl/check check status: success (5ec4d97bd5976823cb925dbbaaffd43f20c49736)
Details
5ec4d97bd5
zuul commented 2025-05-27 12:00:10 +00:00
Member
Copy Link

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/01299e660222471fba5d76948920efc3

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/01299e660222471fba5d76948920efc3 - [otc-tox-pep8 ](https://zuul.otc-service.com/t/gl/build/247f54aa49a14b718fa29da8c3cbc445): SUCCESS in 1m 43s - [otc-tox-py39 ](https://zuul.otc-service.com/t/gl/build/c58eabbdb53e4c62a62cb302d75a2ef0): SUCCESS in 2m 09s
tischrei requested changes 2025-06-10 13:30:35 +00:00
otc_metadata/data/documents/ucs-api-ref.yaml Outdated
@ -0,0 +1,11 @@
---
environment: public
tischrei commented 2025-06-10 13:30:12 +00:00
Owner
Copy Link

internal

internal
otc_metadata/data/documents/ucs-umn.yaml Outdated
@ -0,0 +1,11 @@
---
environment: public
tischrei commented 2025-06-10 13:30:20 +00:00
Owner
Copy Link

internal

internal
otc_metadata/data/services/ucs.yaml Outdated
@ -0,0 +1,16 @@
---
environment: public
tischrei commented 2025-06-10 13:30:29 +00:00
Owner
Copy Link

internal

internal
tischrei commented 2025-06-10 13:32:49 +00:00
Owner
Copy Link

Hi @oeotvos,

we have introduced new metadata platform which can be found in otc-metadata-rework. Helpcenter is already using the data from there. Nevertheless we should make sure that we have this data already in the old repo as well while we are transitioning the tools. So it would be good if you could change your PR according to my comments. We should always start with “internal” that we make sure we don’t provide not approved data somewhere.

Hi @oeotvos, we have introduced new metadata platform which can be found in otc-metadata-rework. Helpcenter is already using the data from there. Nevertheless we should make sure that we have this data already in the old repo as well while we are transitioning the tools. So it would be good if you could change your PR according to my comments. We should always start with "internal" that we make sure we don't provide not approved data somewhere.
oeotvos added 1 commit 2025-06-23 11:09:28 +00:00
merge upstream
All checks were successful
gl/check check status: success (3ead2ac68dc3b2db1ba7a6f2b4f1fd6e86cbaab3)
Details
3ead2ac68d
zuul commented 2025-06-23 11:12:00 +00:00
Member
Copy Link

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/a339f4f836f3475eaef60c8725ef1b74

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/a339f4f836f3475eaef60c8725ef1b74 - [otc-tox-pep8 ](https://zuul.otc-service.com/t/gl/build/d65b5a0159bc4baca7afa48c0a43d27e): SUCCESS in 1m 42s - [otc-tox-py39 ](https://zuul.otc-service.com/t/gl/build/83343be6bdfa44db9204527a103b10c6): SUCCESS in 2m 08s
oeotvos added 1 commit 2025-06-23 11:13:13 +00:00
New service UCS | public -> internal
All checks were successful
gl/check check status: success (7752ff0d10db710ef80c06386ab89871b1ad4913)
Details
7752ff0d10
zuul commented 2025-06-23 11:15:54 +00:00
Member
Copy Link

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/75145ed6c5cf473296b654ff2e0ca455

Build succeeded. https://zuul.otc-service.com/t/gl/buildset/75145ed6c5cf473296b654ff2e0ca455 - [otc-tox-pep8 ](https://zuul.otc-service.com/t/gl/build/d3be1c78bb494e1c91bd285c74a4de3b): SUCCESS in 1m 42s - [otc-tox-py39 ](https://zuul.otc-service.com/t/gl/build/59818c745d834739b0f03d3c79dc8f07): SUCCESS in 2m 21s
oeotvos commented 2025-06-23 11:34:30 +00:00
Author
Contributor
Copy Link

Hi @tischrei, thanks, I changed to internal. And I see that you also added the UCS to rework repo. I’m not sure now how to proceed to be able to start zuul rendering jobs for: docs/doc-exports#1578 docs/doc-exports#1579 Thank you.

Hi @tischrei, thanks, I changed to internal. And I see that you also added the UCS to rework repo. I'm not sure now how to proceed to be able to start zuul rendering jobs for: https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls/1578 https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls/1579 Thank you.
All checks were successful
gl/check check status: success (7752ff0d10db710ef80c06386ab89871b1ad4913)
Required
Details
This pull request doesn't have enough required approvals yet. 0 of 1 approvals granted from users or teams on the allowlist.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u main:oeotvos-main
git checkout oeotvos-main
Sign in to join this conversation.
Reviewers
No Reviewers
tischrei
Labels
Clear labels
gate
Gate it
gate
Gate it
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
A200014817 ansideln cicd ikvrivis magnus otcbot proposalbot sgode smartyno tischrei vhasko vladimirhasko vladimirvshivkov vvshivko zuul
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infra/otc-metadata#310
No description provided.
Delete Branch "oeotvos/otc-metadata:main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?