Page MenuHomePhabricator

Slst2020 (Slavina S)
Software Engineer

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Wednesday

  • Clear sailing ahead.

User Details

User Since
Oct 7 2020, 6:01 PM (183 w, 4 d)
Availability
Available
IRC Nick
blancadesal
LDAP User
Slavina Stefanova
MediaWiki User
SStefanova (WMF) [ Global Accounts ]

Recent Activity

Fri, Apr 12

Slst2020 updated the task description for T362299: [api-gateway] Add a python server to serve consolidated openapi docs.
Fri, Apr 12, 12:55 PM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)
Slst2020 created T362390: [docs] update READMEs.
Fri, Apr 12, 10:09 AM ยท Toolforge
Slst2020 created T362389: [lima-kilo] toolforge_deploy_mr.py confusing message.
Fri, Apr 12, 9:15 AM ยท Toolforge
Slst2020 renamed T362066: [component-api] Develop the webhook mechanism to trigger a deployment from [component-api] Develop the webhook mechanism to trigger a deploment to [component-api] Develop the webhook mechanism to trigger a deployment.
Fri, Apr 12, 6:57 AM ยท Toolforge

Thu, Apr 11

Slst2020 changed the status of T341065: [builds-api,components-api] Automatically deploy the webservice when the image is built from Duplicate to Resolved.
Thu, Apr 11, 3:32 PM ยท Toolforge (Toolforge iteration 08), cloud-services-team, User-dcaro, Cloud-Services-Origin-Team, Cloud-Services-Worktype-Project
Slst2020 changed the status of T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job from Resolved to Invalid.
Thu, Apr 11, 3:32 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T362299: [api-gateway] Add a python server to serve consolidated openapi docs from Open to In Progress.
Thu, Apr 11, 3:31 PM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T341065: [builds-api,components-api] Automatically deploy the webservice when the image is built, a subtask of T194332: [Epic,builds-api,orchestrator,webservice,jobs-api] Make Toolforge a proper platform as a service with push-to-deploy and build packs, from Duplicate to Resolved.
Thu, Apr 11, 3:31 PM ยท Toolforge, cloud-services-team (FY2023/2024-Q3-Q4), Goal, User-dcaro, Cloud-Services-Origin-Team, Cloud-Services-Worktype-Project, Cloud Services Proposals, Epic
Slst2020 changed the status of T362299: [api-gateway] Add a python server to serve consolidated openapi docs, a subtask of T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client, from Open to In Progress.
Thu, Apr 11, 3:30 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero
Slst2020 updated the task description for T362299: [api-gateway] Add a python server to serve consolidated openapi docs.
Thu, Apr 11, 3:29 PM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)
Slst2020 added a comment to T361895: owidm storage quota request.

+1

Thu, Apr 11, 9:36 AM ยท Cloud-VPS (Quota-requests)
Slst2020 updated the task description for T362299: [api-gateway] Add a python server to serve consolidated openapi docs.
Thu, Apr 11, 8:57 AM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)
Slst2020 added a comment to T362299: [api-gateway] Add a python server to serve consolidated openapi docs.

For the deployment we can reuse the same that's there already and add two containers

Thu, Apr 11, 8:49 AM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)
Slst2020 created T362299: [api-gateway] Add a python server to serve consolidated openapi docs.
Thu, Apr 11, 8:08 AM ยท Patch-For-Review, User-aborrero, Toolforge (Toolforge iteration 08)

Wed, Apr 10

Slst2020 updated the task description for T356301: [harbor] Deploy with Helm.
Wed, Apr 10, 8:15 AM ยท Toolforge, User-Raymond_Ndibe, User-aborrero, cloud-services-team (FY2023/2024-Q3-Q4), Goal
Slst2020 closed T361007: [builds-api] builds-api is missing a software license as Resolved.
Wed, Apr 10, 7:31 AM ยท Toolforge (Toolforge iteration 08), Software-Licensing

Mon, Apr 8

bd808 awarded T362062: [Session] Toolforge & Cloud VPS demos a Like token.
Mon, Apr 8, 3:07 PM ยท Wikimedia-Hackathon-2024
apaskulin awarded T362068: [Toolforge & Cloud VPS] Documentation Wish-a-thon a Love token.
Mon, Apr 8, 2:18 PM ยท Documentation, Wikimedia-Hackathon-2024
Slst2020 created T362068: [Toolforge & Cloud VPS] Documentation Wish-a-thon.
Mon, Apr 8, 12:44 PM ยท Documentation, Wikimedia-Hackathon-2024
Slst2020 created T362062: [Session] Toolforge & Cloud VPS demos.
Mon, Apr 8, 12:21 PM ยท Wikimedia-Hackathon-2024

Fri, Apr 5

Slst2020 awarded T361309: [Session] Puppet a Love token.
Fri, Apr 5, 1:00 PM ยท Wikimedia-Hackathon-2024
Slst2020 updated the task description for T361309: [Session] Puppet.
Fri, Apr 5, 1:00 PM ยท Wikimedia-Hackathon-2024
Slst2020 changed the status of T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job from Invalid to Resolved.
Fri, Apr 5, 12:54 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 closed T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job as Invalid.
Fri, Apr 5, 12:53 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a comment to T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job.

Indeed, this seems to have been an issue only in (my particular setup of) lima-kilo. Sorry for the confusion! Non-admin permissions are not broken in Harbor 2.10. Closing this as invalid and moving on.

Fri, Apr 5, 12:52 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 closed T354507: [harbor] upgrade to 2.10.1 as Resolved.
Fri, Apr 5, 12:52 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 closed T354507: [harbor] upgrade to 2.10.1, a subtask of T352417: [maintain-harbor] Manage project quotas via maintain-harbor, as Resolved.
Fri, Apr 5, 12:50 PM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 closed T354507: [harbor] upgrade to 2.10.1, a subtask of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds, as Resolved.
Fri, Apr 5, 12:50 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 closed T354507: [harbor] upgrade to 2.10.1, a subtask of T361708: [harbor, builds-builder] Audit robot account permissions, as Resolved.
Fri, Apr 5, 12:50 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 closed T354507: [harbor] upgrade to 2.10.1, a subtask of T361698: [maintain-harbor] Have maintain-harbor use a robot account, as Resolved.
Fri, Apr 5, 12:50 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 updated the task description for T354507: [harbor] upgrade to 2.10.1.
Fri, Apr 5, 12:49 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 added a comment to T361804: Decision request - Update python team best practices.

I do think that it's good to keep the page somewhat updated, so if you are creating a new repo or similar you have a reference to look up for (as it is, I would probably re-invent whatever checks I used in some other random repo instead).

Fri, Apr 5, 9:01 AM ยท Cloud Services Proposals
Slst2020 added a comment to T361804: Decision request - Update python team best practices.

I don't see that we have to be explicit in the wiki page about what we currently do, other than recommending "follow the conventions in whatever repository you are contributing to", "dare propose changes as you see fit", and if you start a new repository "use common sense and consult with whomever else will be the main contributors".

Fri, Apr 5, 8:50 AM ยท Cloud Services Proposals
Slst2020 added a comment to T361804: Decision request - Update python team best practices.

I think there might be something not clear in the options xd

Anything with 'B' in front is non-prescriptive (A -> prescriptive, B -> non-prescriptive), the number is just the checks to do (if paired with A then in a prescriptive manner, if paired with B in a non-prescriptive one).

Can you elaborate on why you see B1 as the only one non-prescriptive? (so I can modify the wording/etc.)

Fri, Apr 5, 8:32 AM ยท Cloud Services Proposals
Slst2020 added a comment to T361804: Decision request - Update python team best practices.

I want option 1 because it's the only one that is not prescriptive. To me it's a coincidence that option 5 aligns with what I think would happen by going with B1. That said, if the majority vote is B5, I'm fine with that.

Fri, Apr 5, 8:13 AM ยท Cloud Services Proposals
Slst2020 awarded T358496: [toolforge,storage] Provide per-tool access to cloud-vps object storage a Love token.
Fri, Apr 5, 8:04 AM ยท cloud-services-team, Toolforge
Slst2020 added a comment to T361804: Decision request - Update python team best practices.

My preference would be to continue with what I perceive is the status quo, which I would describe as something like this:

Fri, Apr 5, 7:19 AM ยท Cloud Services Proposals

Thu, Apr 4

Slst2020 added a comment to T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job.

Upon further investigation, this seems to have been an artifact of my lima-kilo harbor instance, where I had a few test projects that weren't created/admin'd by maintain-harbor. I will do a bit more testing, but hopefully this turns out to be a non-issue.

Thu, Apr 4, 3:12 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 claimed T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job.
Thu, Apr 4, 2:16 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 created T361842: [harbor, maintain-harbor] Harbor upgrade 2.10 breaks delete-stale-toolforge-artifacts cron job.
Thu, Apr 4, 2:15 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a comment to T361007: [builds-api] builds-api is missing a software license.
Thu, Apr 4, 1:01 PM ยท Toolforge (Toolforge iteration 08), Software-Licensing
Slst2020 updated the task description for T354507: [harbor] upgrade to 2.10.1.
Thu, Apr 4, 12:48 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 added a comment to T361007: [builds-api] builds-api is missing a software license.

To clarify, do we want AGPL-3.0-only or AGPL-3.0-or-later?

Thu, Apr 4, 7:37 AM ยท Toolforge (Toolforge iteration 08), Software-Licensing
Slst2020 changed the status of T361007: [builds-api] builds-api is missing a software license from Open to In Progress.
Thu, Apr 4, 7:21 AM ยท Toolforge (Toolforge iteration 08), Software-Licensing
Slst2020 claimed T361007: [builds-api] builds-api is missing a software license.
Thu, Apr 4, 7:20 AM ยท Toolforge (Toolforge iteration 08), Software-Licensing
Slst2020 changed the status of T358203: [k8s] Add node anti-affinity topologySpreadConstraints to infrastructure components where relevant from Open to In Progress.
Thu, Apr 4, 6:53 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 changed the status of T358203: [k8s] Add node anti-affinity topologySpreadConstraints to infrastructure components where relevant, a subtask of T355883: Create a pool of NFS-less Toolforge Kubernetes workers, from Open to In Progress.
Thu, Apr 4, 6:51 AM ยท Patch-For-Review, Toolforge (Toolforge iteration 06)

Wed, Apr 3

Slst2020 added a comment to T361007: [builds-api] builds-api is missing a software license.

To do this right, we need to add a license notice to every file in the repo in addition to a COPYING file. Is that correct?

Wed, Apr 3, 3:14 PM ยท Toolforge (Toolforge iteration 08), Software-Licensing
Slst2020 changed the status of T351092: [harbor,docs] Improve Harbor quota handling and docs from Stalled to In Progress.
Wed, Apr 3, 2:50 PM ยท Toolforge (Toolforge iteration 08), Documentation
Slst2020 moved T351092: [harbor,docs] Improve Harbor quota handling and docs from Blocked/Paused to Next Up on the Toolforge (Toolforge iteration 07) board.
Wed, Apr 3, 2:49 PM ยท Toolforge (Toolforge iteration 08), Documentation
Slst2020 added a subtask for T361708: [harbor, builds-builder] Audit robot account permissions: T361698: [maintain-harbor] Have maintain-harbor use a robot account.
Wed, Apr 3, 2:48 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a parent task for T361698: [maintain-harbor] Have maintain-harbor use a robot account: T361708: [harbor, builds-builder] Audit robot account permissions.
Wed, Apr 3, 2:48 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a parent task for T354507: [harbor] upgrade to 2.10.1: T361708: [harbor, builds-builder] Audit robot account permissions.
Wed, Apr 3, 2:47 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 added a subtask for T361708: [harbor, builds-builder] Audit robot account permissions: T354507: [harbor] upgrade to 2.10.1.
Wed, Apr 3, 2:47 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 created T361708: [harbor, builds-builder] Audit robot account permissions.
Wed, Apr 3, 2:47 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a subtask for T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds: T361698: [maintain-harbor] Have maintain-harbor use a robot account.
Wed, Apr 3, 12:39 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a parent task for T361698: [maintain-harbor] Have maintain-harbor use a robot account: T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds.
Wed, Apr 3, 12:39 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a subtask for T352417: [maintain-harbor] Manage project quotas via maintain-harbor: T361698: [maintain-harbor] Have maintain-harbor use a robot account.
Wed, Apr 3, 12:36 PM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 added a parent task for T361698: [maintain-harbor] Have maintain-harbor use a robot account: T352417: [maintain-harbor] Manage project quotas via maintain-harbor.
Wed, Apr 3, 12:36 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 added a parent task for T354507: [harbor] upgrade to 2.10.1: T361698: [maintain-harbor] Have maintain-harbor use a robot account.
Wed, Apr 3, 12:35 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 added a subtask for T361698: [maintain-harbor] Have maintain-harbor use a robot account: T354507: [harbor] upgrade to 2.10.1.
Wed, Apr 3, 12:35 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 created T361698: [maintain-harbor] Have maintain-harbor use a robot account.
Wed, Apr 3, 12:34 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds from Stalled to Open.
Wed, Apr 3, 12:04 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T352417: [maintain-harbor] Manage project quotas via maintain-harbor from Stalled to Open.
Wed, Apr 3, 12:03 PM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 changed the status of T352417: [maintain-harbor] Manage project quotas via maintain-harbor, a subtask of T351092: [harbor,docs] Improve Harbor quota handling and docs, from Stalled to Open.
Wed, Apr 3, 12:03 PM ยท Toolforge (Toolforge iteration 08), Documentation
Slst2020 moved T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds from Blocked/Paused to Next Up on the Toolforge (Toolforge iteration 07) board.
Wed, Apr 3, 12:03 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 moved T352417: [maintain-harbor] Manage project quotas via maintain-harbor from Blocked/Paused to Next Up on the Toolforge (Toolforge iteration 07) board.
Wed, Apr 3, 12:02 PM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 moved T354507: [harbor] upgrade to 2.10.1 from In Progress to In Review on the Toolforge (Toolforge iteration 07) board.
Wed, Apr 3, 11:53 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 updated the task description for T354507: [harbor] upgrade to 2.10.1.
Wed, Apr 3, 8:41 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1 from Open to In Progress.
Wed, Apr 3, 8:30 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T352417: [maintain-harbor] Manage project quotas via maintain-harbor, from Open to In Progress.
Wed, Apr 3, 8:30 AM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds, from Open to In Progress.
Wed, Apr 3, 8:29 AM ยท Toolforge (Toolforge iteration 08)

Wed, Mar 20

Slst2020 added a comment to T360509: [harbor,infra] Find a way to manage toolforge project policies with code.

Note also that maintain-harbor already manages the policies for all the other projects in harbor.

Wed, Mar 20, 10:43 AM ยท Toolforge
Slst2020 created T360509: [harbor,infra] Find a way to manage toolforge project policies with code.
Wed, Mar 20, 10:02 AM ยท Toolforge

Tue, Mar 19

Slst2020 renamed T354270: [harbor] Investigate new robot account permissions in Harbor 2.10.0 from [harbor] Investigate new robot account permissions in Harbor 2.10 to [harbor] Investigate new robot account permissions in Harbor 2.10.0.
Tue, Mar 19, 12:49 PM ยท Toolforge Build Service, Toolforge (Toolforge iteration 02)
Slst2020 renamed T354507: [harbor] upgrade to 2.10.1 from [harbor] upgrade to 2.10.x to [harbor] upgrade to 2.10.1.
Tue, Mar 19, 7:26 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T352417: [maintain-harbor] Manage project quotas via maintain-harbor, from Stalled to Open.
Tue, Mar 19, 7:22 AM ยท Toolforge (Toolforge iteration 08), Upstream, Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds, from Stalled to Open.
Tue, Mar 19, 7:22 AM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1 from Stalled to Open.
Tue, Mar 19, 7:22 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review
Slst2020 moved T354507: [harbor] upgrade to 2.10.1 from Blocked/Paused to Next Up on the Toolforge (Toolforge iteration 07) board.
Tue, Mar 19, 7:22 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review

Mon, Mar 18

Slst2020 added a comment to T245683: Find and fix inaccuracies in Toolforge Django tutorial.

Using the new Build Service is now the recommended method for deploying Django applications on Toolforge. I think a better idea would be to:

Mon, Mar 18, 9:14 AM ยท Wikimedia-Hackathon-2024, good first task, Toolforge, Documentation

Mar 15 2024

Slst2020 closed T358100: [toolforge API] expose all backend APIs OpenAPI specs as Resolved.
Mar 15 2024, 11:46 AM ยท Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 closed T358100: [toolforge API] expose all backend APIs OpenAPI specs, a subtask of T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client, as Resolved.
Mar 15 2024, 11:46 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero
Slst2020 moved T356523: [jobs-api] introduce OpenAPI to jobs framework from In Progress to Done on the Toolforge (Toolforge iteration 07) board.
Mar 15 2024, 11:45 AM ยท Toolforge (Toolforge iteration 07), User-aborrero
Slst2020 updated the task description for T358100: [toolforge API] expose all backend APIs OpenAPI specs.
Mar 15 2024, 11:45 AM ยท Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T360147: [envvars-api, envvars-cli] Create envvar name error message is not user friendly.

The current error message probably comes from the envvars API that envvars-cli talks to. The repo is here: https://gitlab.wikimedia.org/repos/cloud/toolforge/envvars-api

Mar 15 2024, 7:12 AM ยท Toolforge
Slst2020 renamed T360147: [envvars-api, envvars-cli] Create envvar name error message is not user friendly from [envvars-cli] Create envvar name error message is not user friendly to [envvars-api, envvars-cli] Create envvar name error message is not user friendly.
Mar 15 2024, 6:53 AM ยท Toolforge

Mar 14 2024

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

Do we want to expose the /healthz and /metrics endpoints in the unified spec?

Mar 14 2024, 3:01 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero

Mar 13 2024

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

operationIds need to be unique. At what level do we want to deal with this? Enforce a naming convention across the individual APis such as {serviceName}_{resourceName}_{operation}? Prefixing when merging the specs?

Not really, that can be dropped if needed, it's only used for code generation I think.

Hmm, we do want to generate the client libraries that we will use in the consolidated CLI, though. Also, I think tools that generate documentation rely on the uniqueness of operationId to correctly link operations to descriptions, parameters, and responses.

Mar 13 2024, 11:05 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

operationIds need to be unique. At what level do we want to deal with this? Enforce a naming convention across the individual APis such as {serviceName}_{resourceName}_{operation}? Prefixing when merging the specs?

Mar 13 2024, 10:50 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro How should we deal with the security top-level element. We are currently ignoring it. Maybe add it to the base.yaml?

Mar 13 2024, 9:55 AM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero

Mar 12 2024

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro thanks! Another question: each openapi spec has it's own /openapi.json endpoint. We will want the gateway to expose the unified spec created by merging the files. Should we remove the individual /openapi.json endpoints from the merged spec?

Mar 12 2024, 4:06 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro what is the base.yaml in your script?

Mar 12 2024, 1:35 PM ยท Toolforge (Toolforge iteration 08), Patch-For-Review, User-aborrero

Mar 11 2024

Slst2020 added a comment to T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

@dcaro What is our plan for creating the Toolforge CLI from the autogenerated SDK? Manually? Automatically with a post-generation script?

Will depend on the quality of the code generated, though I expect that there will always be some manual things we want to check, we could easily just create a new MR with the changes when any of the APIs is changed, for someone to review and merge right away if possible, or manually adapt if not.

Mar 11 2024, 2:57 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 updated subscribers of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

@dcaro What is our plan for creating the Toolforge CLI from the autogenerated SDK? Manually? Automatically with a post-generation script?

Mar 11 2024, 2:34 PM ยท Toolforge (Toolforge iteration 08)

Mar 8 2024

Slst2020 added a comment to T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

OpenAPI Ggenerator and Swagger Codegen look very similar on the surface. A little digging reveals that OpenAPI Generator was forked from Swagger Codegen in 2018 by a group of the Swagger Codegen community and contributors who wanted to proceed in a slightly different direction. Their stated goals were to speed up development and acceptance of new features, improve the quality and maintainability of the code base, and make it easier for new contributors to get involved.

Mar 8 2024, 2:58 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 updated the task description for T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.
Mar 8 2024, 2:12 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation from Open to In Progress.
Mar 8 2024, 1:16 PM ยท Toolforge (Toolforge iteration 08)
Slst2020 changed the status of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation, a subtask of T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs, from Open to In Progress.
Mar 8 2024, 1:15 PM ยท Toolforge (Toolforge iteration 08), Epic

Mar 7 2024

Slst2020 created T359558: [envvars-cli] Either hide or show envvars values, but not both.
Mar 7 2024, 3:17 PM ยท Toolforge