Enable account for 'sectracker' role account

Hi

First of all thanks for setting up the replacement.

Whilest trying to work on the future of the security-tracker we would need as well the 'sectracker' role account to have commit access to the security-tracker project (it's not yet set up), e.g. for the automatic CVE list updates triggered from the security-tracker.d.o host.

Could you thus please cerate a non-guest suffixed 'sectracker' (associated with sectracker@d.o) account for salsa.d.o?

Regards, Salvatore

This is not the best idea, projects can have so called "deploy keys" which can be set in settings/repository of a project. I don't see any need for a role account at this point. More info https://docs.gitlab.com/ce/ssh/README.html#deploy-keys.

What do you think?

Hi,

On Tue, Dec 26, 2017 at 01:37:57PM +0000, Alexander Wirt wrote:

Alexander Wirt started a new discussion:

This is not the best idea, projects can have so called "deploy keys" which can be set in settings/repository of a project. I don't see any need for a role account at this point. More info https://docs.gitlab.com/ce/ssh/README.html#deploy-keys.

What do you think?

Thank you Alexander.

That indeed should suffice for our need to thave the sectracker push the automatic updates.

yes?

@formorer, I replied via mail and starting from the quote the message was cuted. I have pasted it above. In short, yes that should suffice then our needs to have the automatic updates done from the security-tracker to the repository.

Great, I will close this issue now.

closed

added Unrelated label