search

eclipse-tractusx / sig-infra

Apache License 2.0
2 stars 2 forks source link

GitHub: New fork of policy-hub #335

Closed Phil91 closed 8 months ago

Phil91 commented 8 months ago

repository name within Tractus-X Organisation: policy-hub

repository name within Catena-X NG Organisation: tx-policy-hub

GitHub team to grant access: If possible exactly like tx-portal-backend but with a new team for the policy-hub, since it's possible that portal-team will not develop it the whole time.

Thanks in advance

/cc @evegufy

SebastianBezold commented 8 months ago

Hi @Phil91,

I created the fork and granted maintain access for the portal team. I can also create a new team if necessary and add you as team maintainer. The you could add as many other colleagues as you like. Alternatively, we could also grant other existing teams maintain access to the fork. What do you think works best?

EDIT: Here's the direct link https://github.com/catenax-ng/tx-policy-hub

Phil91 commented 8 months ago

Hi @Phil91,

I created the fork and granted maintain access for the portal team. I can also create a new team if necessary and add you as team maintainer. The you could add as many other colleagues as you like. Alternatively, we could also grant other existing teams maintain access to the fork. What do you think works best?

Thanks @SebastianBezold

I think for now the portal team is perfect since we're developing it for now. If it changes I'll come back to you :)

SebastianBezold commented 8 months ago

Ah perfect, then I'll close the issue for now

Phil91 commented 7 months ago

@SebastianBezold just came to the topic that I wanted to add some secrets to the tx-policy-hub repo, but missing the permissions, same for @evegufy should I reopen the issue or create a new issue for requesting the permission?

FaGru3n commented 7 months ago

@SebastianBezold just came to the topic that I wanted to add some secrets to the tx-policy-hub repo, but missing the permissions, same for @evegufy should I reopen the issue or create a new issue for requesting the permission?

@SebastianBezold is on leave today new issue should be fine... then we can create some more secrets on the org on your desired repo...

best practice... hint us where to find the secrets in your vault secret engine

evegufy commented 7 months ago

@FaGru3n thanks for replying! We need to have the secret available in the GH action env, so the most forward way is to use secrets at repo level, like we're already doing it in the e2e-testing workflow in the portal-backend. If some more context is needed, we're glad to explain in a quick call.