Kent Rancourt
Kent Rancourt
> Have you considered slog which was introduced in go 1.21?" I'd be open to a cook-off, but would also want to hear @jessesuen's opinion.
@webstradev we're super appreciative of the assistance.
Pulling this into v0.6.0 purely on the basis of being low-hanging fruit. It can be deferred if necessary.
@joebowbeer I don't think this is something that can realistically be handled at the pod level. Kargo's credentials are managed at the Project level. This means that two Projects can...
> I interpret what you're saying to mean that, in Kargo, some inherent container identity can't be used to obtain the AWS creds. Essentially, yes. To re-iterate the problem I...
@isugimpy thanks for the suggestion. I can see how this is a problem for you. The reason for the current behavior is that it is meant to prevent "hijacking" an...
> That's actually why I suggested a gate on the CR saying that Project is allowed to share ownership of the namespace, so that it isn't the default, but rather...
Agree it's ideally a back end change. Re-labeling accordingly.
Looks like the upgraded eslint doesn't work with the existing eslint configuration.