cicd

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

The Argo CD CLI throws a misleading warning about cluster level privileges when adding a cluster with namespace level privileges.

Only the warning looks wrong, the cluster is

Spug运维平台在过去的公司里稳定运行6年以上，开源的大部分代码也是基于稳定版本之上，为了增加更多用户在企业使用的信心，如您愿意，请将您在企业中使用Spug的案例展示给我们，请在该issue页面提供您的使用案例，提交格式：企业名称 + 公司官网地址。官网地址为可选项，您可以直接提供企业名称即可。

此外，您也可以通过其他渠道如QQ、微信、邮件的方式联系项目作者提供使用案例。

征集长期有效，感谢大家支持！

Spug部分案例：

• 上海家谐网络科技有限公司
• 上海爱上慧家信息技术有限公司
• 南京白鸥网络技术有限公司
• 杭州中艺实业股份有限公司
• [北京步鼎方舟科技有限公司](http://

@ktsakalozos I'm currently using multiple microk8s clusters and found the below tools quite useful and think that they could be a great addition to the list of add-ons.
Brief description of potential add-ons:

• Loki: Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is de

SUMMARY

While using the action runner type "local-shell-script", the action always try to set execute permission for the action script before the execution.

For example, action runner logs for the core.sendmail action

2022-03-09 07:02:06,866 INFO [-] Executing action via LocalRunner: dcc6c28d-5674-4cc2-9174-ca6c1e7b23a3
2022-03-09 07:02:06,866 INFO [-] [Action info] name: sendm

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins

Docker volumes are supported in GH via yaml definitions. We should tell this instead of just throwing an unsupported error.

Through staticcheck, we found the Invalid struct tag problem, which needs to be fixed:

Hi! We are working on improving access control for the Database Lab Engine.

The primary focus is LDAP, Active Directory, SSO support for clones and UI/CLI connections, granular control over user permissions.

See more details and comments on GitLab issue #315.

Your contributions are very welcome to support our open-source prod

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Description

GitHub released an option to disable the auto update of runners. https://github.blog/changelog/2022-02-01-github-actions-self-hosted-runners-can-now-disable-automatic-updates/ Now we can add an option to support this by the module

Default

Question is what should be the default?

• Without AMI. Keep the current behaviror. With the S3 we haven't any issue for months.

Hi,

We are using terraform-aws-gitlab-runnner to spin up GitLab runners on our AWS account. As part of security auditing, there was a severe alert raised on this policy created by terraform module: https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/policies/instance-docker-machine-policy.json#L21

The problem lies with permitting IamPassrole action on all resources. As per